Hello,

There is a reference to 11.1.20111.2111 somewhere in your application.  These are the places that are possible to find the reference:

• license.licx (this typically is a compile time error rather than runtime).
• References in the project – typically this would also be caught at compile time.
• Compiled dependencies containing user controls or code libraries with Infragistics references – if these were compiled with the newer version, this might be seen at compile time or run time.
• If there are any Binary references in a resource file they could have a reference to a specific version.

Is it possible to get the call stack for the crash?  This might give some hints as to what is causing the issue.  This should be in the exception details.

Note that by default when doing .NET development and debugging Visual Studio is set to skip over code that you don't have debug symbols for so that will cause it to skip over the Application.Run method when you step through the code.  You can uncheck the Enable Just My Code option in the debugger options and enable Framework Source Stepping to change this behavior.

Let me know if you have any questions with this matter.

To bind the WebDataGrid to data, you would set it's DataSource property and to do this you either need access to the control from outside the user control or you need access to the data source you which to set from inside the user control.  This would be the same for accessing the property of any control that is on the UserControl from the containing page and isn't specific to the Infragistics controls.

Here are a few possible ways to do this:

• Expose a property for the DataSource on the UserControl so that you can set that and within the UserControl you can use it.  See User Control – Custom Properties on StackOverflow for an example of this approach.
• Exposing the grid as a property on the UserControl so that you have access to it from the parent page. 
• Find the control with FindControl from the parent page.

Let me know if you have any questions.

Marco,

We added support for the XLSX format in our Excel Engine in the 2008 Volume 3 release of NetAdvantage which was near the end of 2008.  If the third party application doesn't support XLSX then it is up to the third party application provider to either update the assemblies used in the application to be from the 2008 Volume 3 release or later or if already using a version of the excel engine that has XLSX support they would need to modify the code of the application so that that the XLSX format is used rather than XLS.

Let me know if you have any questions.

Fidencio,

The older installers may incorrectly interpret formatting characters as part of the key which could make the key invalid.  This result is often cached until the machine that you are installing on is restarted.  Please restart your machine and type the key into the installer or copy it from a source that doesn't have rich text formatting like Notepad.

Let us know if you have any questions with this matter.

Sri,

The objects defined in the markup don't have instances created when creating the UserControl with new.  To address this, use Page.LoadControl to instantiate the UserControl to address this.  The same issue is addressed in the following question on stackoverflow:

http://stackoverflow.com/questions/2275625/asp-net-custom-user-control-to-add-dynamically

Let me know if you have any questions with this matter.

Shamroz,

The developers guide in the online documentation is a good place to start learning more about the controls.  For the grid, a good topic to start with is Getting Started with WebDataGrid.

Tilmann,

Thank you for sharing the solution, I hadn't seen that KB article before.