SharePoint University

MY requirement is that I have to create custom webpart in that I need to give site url and it will populate the list available in that site(DropDownList) and when I select particular list it will populate views related to that list(DropDownList).My requirement is that I need to display DataView using .NET code

wsswp.DataFormWebPart myDataView = new Microsoft.SharePoint.WebPartPages.DataFormWebPart();

This means that you must set up Xsl or XslLink property. For example:

DataFormWebPart.XslLink = "http://win2003/Style Library/XSL Style Sheets/ContentQueryMain.xsl";

This will set standard SharePoint xsl templates.

You can pass xsl template as test directly  to Xsl property.

I am not able to understand your point Can you be more specific and if possible can you show it by example.My first and main doubt is that in xslLink what should I write

When you create a Data Form Web Part, you need to give it the XSLLink or the XSL property, this property allow the DataForm webpart to display the data source in an Html format. now the object of DataForm web part must initiate the XSL property or XSLLINK property such as following:

DataFormWebPart dfwp = new DataViewWebPart(); 

dfwp.XSLLink = "path for an XSLT file" OR

dfwp.XSL = "<xsl:na.........></xsl>" //you can have a well formed xslt code from opening any dataview web part using Designer 2007

I've got the same problem. The error appears when you click any button created as a server control, when it postback and before any event of the control is fired.

It occurs only when you fill the XSL property directly in code, not when you fill it in the html page or you use the xsllink, even using exactly the same XSLT. I tried to assign the property in other methods/events along all the life cicle of the DFWP with the same problem.

Any idea?

In other way.... anybody knows how to find the code that is generating the error? I tried to use the Reflector to see inside the out-of-the-box DFWP, but I can't find the code that is generating the error.

Hey! I had an idea just writting the last repply... I found that if you assign the XSL property with your XSLT in your code but you also put something between the <XSL> and </XSL> tags in the form (something, it doesn't matter, you'll fill it later with the correct XSLT), the error doesn't occurs! Now in my test project I've got another error on the onbubble event of the button, but, this is another war!