Hi,
I create a users controls using the 7.2 version of infragistics over visual studio 2008. Without problems!
But when I load a proyect with a previous version (6.1 for example) and load the control with 7.2....the enviroment shows me many errors.....and some warnings.
All the errors and warning are about the conflict between namespaces of infragistics.
So, ¿there is a way to fix this? ¿can a project have both version of the infragistics controls without problems?
Thanks....
NetAdvantage 2008 Volume 1 is the first volume in which Visual Studio 2008 is supported. Please refer to Vince McDonald's blog regarding Visual Studio 2008 support here:
http://blogs.infragistics.com/blogs/vmcdonald/archive/2008/01/02/infragistics-support-for-visual-studio-2008.aspx
In regards to you main questions, multiple versions of our controls will not work in the the same project or with projects that reference each other. In your scenario where your user controls were created using 7.2, you wil have to either downgrade your user controls to 6.1 or upgrade your project to 7.2.
Excelent Sung....
So, I have another question: theres a way to upgrade o downgrade a project automatically? From 6.1 to 7.1 or else....
Because make a upgrade for example, step by step....can bring me many errors and problems, there's many control and code.....
thanks
Upgrading and downgrading an application is always a delicate process. The easiest part is getting the application to use the new assemblies. It is the testing you have to do afterwards to make sure there are no problems once making an upgrade or downgrade that can take some time.
If you place this question in the scope of Infragistics controls and Windows Forms, there are a few things to consider. We do maintain backwards compatibility so going back and forth should not be too much of an issue. You just have to change the references to point to the new version and recompile. When downgrading, there are some cases where classes did not exist in 6.1 that exists in 7.2 (ribbon for example) and you will have to remove those elements to get your application to compile in the older version. When going up in a version, you run the risk of functionality being changed, an introduction of a bug or behavior change to fix another bug. With those possible complication aside, there are numerous ways to start step 1 listed in our help article:
http://help.infragistics.com/Help/NetAdvantage/NET/2008.1/CLR2.0/html/Win_Upgrading_Your_Windows_Forms_Projects.html
Part of step 1 and planning for steps 2 can be done by noting some of our documented breaking changes and feature introductions by version:
http://help.infragistics.com/Help/NetAdvantage/NET/2008.1/CLR2.0/html/Win_Whats_New.html