Upgrading to VS 2013 and .NET Framework 4.5.1 Questions! RRS feed

  • Question

  • User-498848506 posted

    I just upgraded my system to VS 2013 Ultimate and .net Framework 4.5.1. My solution was developed using VS 2010 .net Framework 4.0. When I opened the solution for the first time there were some mechanizations going on, and then the development environment opened, seemingly like nothing changed.

    The only way that I could tell if .NET Framework 4.5.1 was working, I beleive, was to force an error.  The resulting error page however still shows
    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18408.

    When I right clicked on the project, selected "Property Pages" and looked at "Build -  Target Framework" the dropdown listed Framework 4. I changed that to .NET Framework 4.5.1

    I might assume that it would now show something along the lines of 4.5.1 on the error, but it did not?

    Did anything change?  Would there be an issue if I were to now move files that were modified with framework 4.5.1 on my developement machine (if it is in-fact working) to the webserver where there are pages that were not converted and I really don't know if .NET 4.5.1 is or is not needed on the webserver.... and will they affect other pages that are already running there?

    I have searched and really found not too much about this kind of upgrade, other than the literature thatI did find saying that it conversion is "automatic" when the solution is opened.... is there perhaps a "Migrating for Dummies" document that explains this whole thing? Do I now have to replace all the pages on the server?

    Thank you for your patience.... I know I have asked many questions.... Thanks!

    Wednesday, May 28, 2014 1:25 PM


  • User-1404016747 posted

    If you set the project to 4.5.1 in the project setting you are using 4.5.1.

    The IIS error page will report 4.0.xxxx due to the fact 4.5.1 installs on top of 4.0 and does not replace it.
    This is also true when using 3.5. Error pages report v2.0.xxx even though 3.5 is present and in use.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Wednesday, May 28, 2014 3:13 PM

All replies