Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
430
Compilation errors using both Classic and Aikido controls
posted

Hi, In our app we have classic retired controls (WebDateChooser, UltraWebTree, Ultrawebtab... etc) and now we are trying to update the application to last control version (2012.1) still using old controls using the 'version free dll' approach, because now is impossible for us to replace thousands of controls in hundreds of forms using the new ones.

So we have followed the instructions of 'http://es.infragistics.com/community/blogs/taz_abdeali/archive/2011/11/17/asp-net-product-changes-in-2011-volume-2.aspx' post and somehow we have managed to make the application work with 2011.2 version of the controls but when we have updated the dlls with the 2012.1 versionfree dlls and we have tried to compile the app we have found errors like:

1) If we overwrite the 2011.2 dlls with the 2012.1 dlls (keeping at the bin dlls that are not in 2012.1 like Infragistics.Web.Ui.Webdatechooser)
-The type or namespace name 'WebCurrencyEdit' does not exist in the namespace 'Infragistics.WebUI.WebDataInput'
-The type 'Infragistics.WebUI.WebSchedule.WebDateChooser' exists in both 'c:\development\Integra\DEV\Web\bin\Infragistics.WebUI.WebSchedule.dll' and 'c:\development\Integra\DEV\Web\bin\Infragistics.WebUI.WebDateChooser.dll'
-The type or namespace name 'ValueChangeEventArgs' does not exist in the namespace 'Infragistics.WebUI.WebDataInput'
among other similar errors...


2) If we delete all the 2011.2 dlls and put at the bin only the 2012.1 dlls
-The type or namespace name 'WebTreeNodeEventArgs' could not be found (are you missing a using directive or an assembly reference?)
-The type or namespace name 'WebDateTimeEdit' does not exist in the namespace 'Infragistics.WebUI.WebDataInput'
-The type or namespace name 'UltraWebNavigator' does not exist in the namespace 'Infragistics.WebUI' (are you missing an assembly reference?)
among other similar errors...

I understand that problem with 2nd option is because dlls like UltraWebNavigator.dll are missing, and problem like 'The type or namespace name 'ValueChangeEventArgs' does not exist in the namespace 'Infragistics.WebUI.WebDataInput'  is because those methods/properties are missing on 2012.2 dll version of WebDataInput... so should we mix 2011.2 and 2012.1 dlls? But then there are errors like the 'The type 'Infragistics.WebUI.WebSchedule.WebDateChooser' exists in both 'c:\development\Integra\DEV\Web\bin\Infragistics.WebUI.WebSchedule.dll' and 'c:\development\Integra\DEV\Web\bin\Infragistics.WebUI.WebDateChooser.dll'' one.  Should we keep the datechooser.dll or not?

From the documentation, help... I really feel that the process to keep using both classic and new controls at the same time is not clear. Could you please help us or provide a clear list of instructions of how to use at the same time classic controls and 2012.1 version of the controls? (The documentation provided, which applyes only for 2011.2 version explains only 'Make sure for all the non-classic controls that you are using, you copy the version-less assemblies for those controls to your applications bin folder as well. You need to use version-less assemblies for both the controls if you want to you classic and non-classic controls together in an application')

Any help would be appreciated. Thanks in advance

Parents Reply Children