We have a Visual Studio 2005 (VB.net) application that was using the NetAdvantage 2007.2 controls. We recently converted this solution/project to Visual Studio 2010 and upgraded the Infragistics controls to 2011.1 using the Version Utility to do the upgrade.
The interesting thing is we can open the solution and build it and run it with no issues. But if we try and open any of the forms in design view that use any Infragistics controls we get a series of errors/warnings. Some of the errors are seeing are:
Warning 41 The variable 'UltraGridColumn9' is either undeclared or was never assigned.
Warning 51 The variable 'UltraGridBand2' is either undeclared or was never assigned.
Warning 22 The variable 'Appearance6' is either undeclared or was never assigned.
Warning 148 Could not find type 'Infragistics.Win.UltraWinMaskedEdit.MaskedEditTabNavigation'. Please make sure that the assembly that contains this type is referenced. If this type is a part of your development project, make sure that the project has been successfully built using settings for your current platform or Any CPU.
Again, the above is just a sample of the errors we are seeing. I should also mention that we are targeting the 4.0 (full) framework.
Any ideas what could be causing these problems and how we can correct them?
Thanks.
Jim
Hello Jim,
Have you been able to sucessfully use the designer on a new sample project with Visual Studio 2010, .NET 4.0, and Infragistics 2011 Volume 1? This will ensure that Visual Studio creates a proper toolbox for the newer version(s) that you install. Also, I recommend clearing the "license.licx" of all Infragistics entries. The file might still be pointing to 2007. Please save the file after it's cleared. Also you should make sure all the Infragistics assemblies referenced in your project have the "Specific Version" property set to false. You may want to clean the solution and rebuild.
Now, if you open the designer, the toolbox should be working correclty.
For more details please visit our online help for further documentation and tips on upgrading.
Hello Michael,
Yes, in answer to your question, we have been able to successfully use Visual Studio 2010 with the 4.0 Framework and Infragistics 2011 Volume 1. We've had no issues creating brand new solutions/projects, as well as, converting older versions of applications to VS2010 and the 2011.1 version of the controls.
I tried what you had suggested. The License.licx file only had references to the 2011.1 controls, but I cleared it out anyway. I also double-checked the "Specific version" property for the Infragistic references and there were a couple that had it set to "True" so I set those to "False". I cleaned the solution and re-built and I am still getting the error messages when I try to open a form in design view. The application still runs fine though.
I've checked out the link for further help on upgrading. Haven't found anything just yet that is helpful, but I'll keep looking. If you have any more suggestions I'm open to hearing them.
Thanks!
I am very glad to hear that you have resolved the issue. Let us know if you have any additional questions moving forward.
Michael,
I found the issue. One of our custom built DLLs was still using an older version of the UltraWinGrid. I mistakenly had assumed that DLL had been updated. I removed it from the references and fixed the accompanying errors and now the forms that had been throwing the error open in design view with no issues. I sincerely appreciate all your help!
Yup, I do have the Infragistics2.Win.UltraWinMaskedEdit.v11.1 as one of my references. Below are all my Infragistic references.
Infragistics2.Documents.Core.v11.1Infragistics2.Documents.Excel.v11.1Infragistics2.Shared.v11.1Infragistics2.Win.Misc.v11.1Infragistics2.Win.UltraWinCalcManager.v11.1Infragistics2.Win.UltraWinDataSource.v11.1Infragistics2.Win.UltraWinDock.v11.1Infragistics2.Win.UltraWinEditors.v11.1Infragistics2.Win.UltraWinGrid.ExcelExport.v11.1Infragistics2.Win.UltraWinGrid.v11.1Infragistics2.Win.UltraWinMaskedEdit.v11.1Infragistics2.Win.v11.1
I haven't had an opportunity to try excluding one of the lines of code to see if that makes a difference with some of the messages. I'll get to that later this afternoon.
Thanks,
Hello,
I wanted to provide some additional information regarding the different warnings are you seeing to assist you troubleshooting the behavior.
"Warning 148"
Please make sure the following assembly is referenced in your project. Infragistics2.Win.UltraWinMaskedEdit.v11.1
Warning 41, 51, 22:
Normally these are extraneous lines of code from once instantiated variables that can potentially me removed. You can test this be exclude one of them and determine if they messages are removed. Otherwise, please provide a list of your references used in your application.
For more details I recommend referring to the following MSDN article
Hello James,
Yes, in most cases, closing and rebuilding the form's project should relieve some of the issues. However, I recommend that you review your designer class file(s) associated with your forms. You may need to "Show All Files" button in Solution Explorer first.
As a general rule, please try not to change/modify generated code. I recommend reviewing the following article.
To further troubleshoot the behavior I'd advise in attaching your project or a smaller one that reproduces the behavior.