none
Any issues downgrading from .Net 4.5 to 4.1 RRS feed

  • Question

  • We have written a web-based online system running on IIS7 for our customer. There are two systems in use, a test system and a 'visible' online production server. Both were running the .Net 4.1 framework.

    Our customer, in his infinite wisdom, installed .Net 4.5 on the production server without advising us. Shortly afterwards we started receiving calls that parts of the production web site were not working as expected. The common factor was rapidly found to be that they were all XP machines running IE8, clearly these are no longer supportable with the newer version of the framework.

    The customer removed .Net 4.5 and reverted to 4.1 but we are now finding strange issues with the production server not working properly. The test system which was not updated works perfectly, as does our own internal test system.

    I notice that the internal version number of .Net 4.1 and 4.5 are actually identical.

    Does anyone know if there are any 'gremlins' left by performing this downgrade?


    Norman

    Thursday, May 9, 2013 9:51 AM

Answers

  • Hi Norman,

    If they want to go back to .NET Framework 4.0 on Windows XP. They will need to remove .NET 4.5 then install .NET 4.0 a second time. After that, they should update Windows Updates to update their OS.

    By the way, what's their server OS version?

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, May 16, 2013 9:04 AM
    Moderator

All replies

  • I am aware of a .NET Micro Framework 4.1 and .NET Framework 4.0. Please clarify which is involved.

    .NET Framework 4.5 is an in-place update to .NET 4.0, so it would be necessary, after removing 4.5 on that server, to repair 4.0.

    To be sure .NET Framework 4.0 is correctly installed and configured on the server, have your client use this tool:

    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    Run the tool with .NET 4.0 selected, then look at the last 15 lines of the tool log for test app results. If the test app exited with return code 0, the framework is OK.

    Thursday, May 9, 2013 12:22 PM
  • Hi Norman,

    Please refer to this page:

    http://msdn.microsoft.com/en-us/library/5a4x27ek.aspx

    Uninstalling the .NET Framework 4.5 also removes pre-existing .NET Framework 4 files. If you want to go back to the .NET Framework 4, you must reinstall it and any updates to it. (See Installing the .NET Framework 4.)

    When you removed .NET 4.5 you have to reinstall .NET 4.0.

    By the way, I'm also not sure .NET 4.1 from your post, please clarify it.

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, May 10, 2013 5:07 AM
    Moderator
  • Thanks for the positive reply.

    Previously they were on 4.0 and the update to 4.1 was applied.  Moving it up to 4.5 without consultation was an act of stupidity.

    We found out what was happening with the XP machines and queried it with the customer, within no time they had taken 4.5 off and got it back to 4.1 so the state of the current system is open to scrutiny.

    To say that we were unhappy about what they did is probably an understatement as we get the calls when it doesn't work properly. As the calls were only from XP users it didn't take that long to make an educated guess at what they had done.

    Currently the production system is experiencing slowness when compared to the test system, despite theoretically being in the state it was in before.

    I always have concerns over registry entries and ini files when something like this happens. And as they say, "It's a darn big haystack"

      


    Norman

    Friday, May 10, 2013 8:03 AM
  • "Previously they were on 4.0 and the update to 4.1 was applied. "

    What 4.1 update? I'm unaware that such an update exists.

    Friday, May 10, 2013 12:00 PM
  • Hi Norman,

    How is your issue now?

    I haven't saw .NET 4.1 update too. A little confused about your issue.

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, May 16, 2013 8:14 AM
    Moderator
  • Well you are correct. They moved back to .Net 4, but is there a patch update on it?

    They were doing there own development on another project without our knowledge using Visual Studio 2012 and the .Net 4.5 environment required for that appears to have been the cause of the original issue. They blindly updated to .Net 4.5 without communicating this with us and then when the calls started coming in initially blamed our development.

    The interesting thing is that they actually run two production servers and the other was not updated to .Net 4.5, they now comment that the one which was not updated is noticably faster than the one that has been moved back.

    As we are just responsible for providing the software we've not been involved in the operating system, IIS and SQL Server setup. Needless to say our test system here works perfectly.

    We have a nightmare customer as their idea of sorting a problem is to roll back installers.

    They are now asking if we have 'ideas' to sort it out. Simple logic says that when they took the .Net back it left something on the system. We would like to move to .Net 4.5 but they have a large userbase on XP at the moment.

    I was just looking for any guru that had taken the 4.5 back and encountered similar issues. I am thinking of things left in config files and registry entries.


    Norman

    Thursday, May 16, 2013 8:54 AM
  • Hi Norman,

    If they want to go back to .NET Framework 4.0 on Windows XP. They will need to remove .NET 4.5 then install .NET 4.0 a second time. After that, they should update Windows Updates to update their OS.

    By the way, what's their server OS version?

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, May 16, 2013 9:04 AM
    Moderator
  • The customer is using 2008 R2

    Their equipment is very high spec.


    Norman

    Thursday, May 16, 2013 9:42 AM