Forums General
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
Close
John Price
739
Questions about trying to upgrade from 2010.3 to 2012.1 while keeping some classic controls
posted

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

Hi –

 

I am a development manager at a company that's been using your controls for about 5 years.  I read the article at http://community.infragistics.com/blogs/taz_abdeali/archive/2011/11/17/asp-net-product-changes-in-2011-volume-2.aspx and agree that this is the right direction.  The new grid especially is much more intuitive that the UltraWebGrid.

 

However, we have set aside the next two weeks to try to upgrade and are having trouble with an upgrade strategy.  We have 6 web apps to be upgraded, which range from 2-3 pages up to almost 300 pages.  The largest ones have a mix of the old grids/tabs/etc. and the newer ones.   What I had hoped to do was upgrade the projects using the Version Utility 2012.1, and then add versionless references for the classic controls to get everything to build.  However after reading the help pages “Using Version Upgrade Utility” and “Version-less Assemblies” it appears this won’t work; also, the Version Utility stops with an error upon finding any classic controls.  

 

It appears the only real option is to try to switch every control to the newer ones before upgrading.  This will be a Herculean effort requiring many weeks for our team.  The plan (I think) would involve:

 

1)      Manually switch each control while still on 10.3.  For a grid it would mean putting a second WebDataGrid below the UltaWebGrid, setting all the columns again manually (since we often don’t use auto binding), then setting up all the event handlers (itembound, databound etc) and replicating all the custom functionality there; and then running the page with both grids, testing, and finally removing the UWG.  Rinse and repeat for many pages. 

2)      After that, upgrade the projects to 12.1 to get the IE9/tablet support we want, and then re-test everything. 

 

Is that the correct way to go about it?  The help talks about swapping out versioned for versionless assemblies on a deploy, then swapping them back to make code changes – but we’re in these apps coding very frequently so that seems impossible.

 

Thanks,

 

John Price

  • 49378
    posted

    Hi John,

    Thank you for posting in the community.

    To answer your query, your planned migration approach makes perfect sense and should be possible without resorting to the version-less assemblies. During this migration process, however, there would be multiple versions of Infragistics assemblies and caution should be employed to not refer multiple versions of the same assembly simultaneously.

    This applies mainly for the assemblies used by the non-retired classic controls such as the WebSchedule and UltraChart and in particular the WebUI.Shared.dll. A useful guide listing the required assemblies for specific controls may be found at:
    http://help.infragistics.com/NetAdvantage/ASPNET/2011.1/CLR4.0/?page=Web_Deployment_Overview.html

    Please do not hesitate to contact me if you need more information regarding this matter.