Planning for upgrade at Q2 2016 node

[Clive Hoggar]

Hi Guys

I am planning to start a new web design project in July and take the opportunity to upgrade from Q2 2013 asp.net ajax toolset to Q2 2016 and move from VS 2012 to VS 2015 community edition at the same time. Production website will be running on iis 7.5. I assume this will be fine...?

However, if I have to use this development setup to maintain or extend an existing website with 2013 controls, what problems might I expect, and how should I avoid them!

 

Thanks for any insights on avoiding action that you can give me before I hit a pothole

Clive

 

[Marin Bratanov]

Hi Clive,

I will try to address each question:

IIS 7.5 is fine, it is supported: http://www.telerik.com/aspnet-ajax/tech-sheets/system-requirements.

On upgrading, I suggest you go through these resources:

• how to upgrade (different options plus step by step guides and troubleshooting tips): http://docs.telerik.com/devtools/aspnet-ajax/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.
• the following sticky thread lists known issues and important changes in our releases that may affect you: http://www.telerik.com/forums/known-issues-and-important-changes. Thus, I advise you review the list and evaluate it based on the features and controls you use. Note that regression bugs are usually fixed with the next release, so you may be potentially affected by issues in the last release and by any breaking change.
• go through the release notes as well as they also list the changes and new bits: http://www.telerik.com/support/whats-new/aspnet-ajax/release-history.

I also advise you disable the BrowserLink feature in VS because it is known to break WebResource requests that our controls use extensively by default.

Regards,

Marin Bratanov
Telerik