We have an ASP.NET Web Forms Application (not a Web Site...it's compiled before it runs) that uses an old version of Infragistics (the DLL names end with v8.1). We'd like to upgrade the application to Infragistics 14.2. The application contains a fairly large number of Infragistics controls. For example, it has over 100 occurrences of UltraWebGrid, some of which use advanced features and are manipulated quite a bit by the C# code-behind.
We're looking for advice on the process (i.e., steps) we should follow to upgrade this application. For example, if we simply replace references to the old Infragistics DLL's with references to the new, compiling the application results in thousands of errors (the application contains over 2,000 files). Since it won't compile, we can't convert and test one control at a time...we have to convert all of them before we can run the app to test any of them. If we wait that long to begin testing, there's a good chance that many of our conversions will be semantically incorrect.
The idea of having the application simultaneously reference both the old and new versions of Infragistics has occurred to us, and that would allow us to convert (and test) one control at a time. But one thread on this forum says that's impossible (http://ko.infragistics.com/community/forums/t/96273.aspx). Another thread says it's possible, but it's a few years older (possibly out of date?) and seems to be talking about a Web Site, not a Web Application. For ASP.NET Web Sites, I believe compilation happens for each individual page when it's requested at run time, and that may be the reason why the old and new Infragistics don't clash in that case (assuming each page is referencing only one of the two Infragistics versions).
Any comments regarding those two threads or the process we should follow to convert our application would be greatly appreciated.
Hello Michael,
Thank you for posting in our forums!
Using two different versions of the Infragistics controls isn’t recommended or possible. Attempting to use multiple versions in the sample project will cause conflicts and the controls won’t know what version of the assemblies to use.
In addition to above information, I would like to post an example from my issues i am facing.Even though i referred the latest Infragistics dll((Version 14.2),it is looking for older version of dll.
Error:
The type 'Infragistics.WebUI.Shared.IProvidesEmbeddableEditor' is definded in an assembly that is not referenced. You must add a reference to assembly 'Infragistics.WebUI.Shared, Version=8.1.000,Culture=neutral,PublicKeyToken=7dd5c3163f2cd0cb'
would like to note that version v8.1 is no longer supported and I would recommend converting from the classic controls to our newer controls and upgrading versions to a supported version. Please let me know if you have any further questions concerning this matter.
Hi Divya,
1) I mentioned that there was a thread on this forum that says using multiple versions of Infragistics in the same project *is* possible (but perhaps only if that project is a Web Site not a Web Application?). The link I'm referring to is http://ko.infragistics.com/community/forums/t/75437.aspx. Is the information in that thread incorrect? If so, it should probably be removed from your site so that other people don't follow its advice.
2) I also asked if there is a recommended process or set of steps that we should follow to upgrade our application from v8.1 to v14.2. Such recommendations are sometimes referred to as "migration paths" and software vendors often provide them to their customers. Does Infragistics offer anything like that to help its customers?
-Michael
Infragistics provide different –different ways for migration of applications and using two different versions of Infragistics controls in the same Web Site is one more ways. but isn’t recommended! every process has their pros and cons. This method might create assembly conflict issue later on.
I would recommend upgrade process for your application from v8.1 to v14.2.
Regarding set of steps and process of migration I will create a case for you and provide the document.