Planning for upgrade at Q2 2016 node

2 posts, 0 answers
  1. Clive Hoggar
    Clive Hoggar avatar
    334 posts
    Member since:
    Nov 2008

    Posted 05 May Link to this post

    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

     

  2. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3595 posts

    Posted 09 May Link to this post

    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:

    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
    Do you need help with upgrading your ASP.NET AJAX, WPF or WinForms projects? Check the Telerik API Analyzer and share your thoughts.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top