none
.Net 3.5 SP1 Backward compatibility RRS feed

  • Question

  • Hi,

    We have one application, currently runs on OS= Windows Server 2003, Framework = .Net 1.1, Web Server = IIS 6.0 and the application was developed using VS2003 and  database SQL Server 2000. I know all technologies are pretty old.

    Question is, Now we have got a new server having OS = Windows Server 2008, Framework= .Net 3.5 SP1, Web Server = IIS 7.0.

    So If we try to move our application to this new server, will the application run ?

    Will there be compatibility issue in terms of 32-bit(old system) to 64-bit(new system) ? What are the other risks associated ?

    Please guide.

    Thanks

    Monday, April 23, 2012 8:03 PM

Answers

  • If the application was written to target .NET Framework 1.1, you will need to install .NET Framework 1.1 on the new server to get it to run as-is.

    As DirkStrauss mentioned, you can upgrade the original solution (if you have it) in either VS 2008 or VS 2010 to target .NET Framework 3.5 so the new version will run on the new server as configured. Both newer VS versions have an Upgrade Wizard that will (semi)automatically convert your old solution to the new VS format and allow you to target .NET 3.5. Of course, if issues arise, they will have to be manually corrected by a developer.

    If you plan on installing 1.1 on your new server, you should read through these threads:

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/614edf55-4cdf-4d6a-bfff-0d803ec60041

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

    Before you select this option, you should be aware of .NET Framework 1.1 end of support dates:

    http://support.microsoft.com/lifecycle/?p1=1249

    • Marked as answer by Jyos Monday, April 23, 2012 9:55 PM
    Monday, April 23, 2012 9:25 PM
  • Hi Jyos

    If you have a Windows Forms Application setup, you will need to rebuild the application for 64 bit PC. But I presume you have a Web Application. Might I make a suggestion. There are many things that can go wrong, especially if you have such a big migration (Windows 2003 to Windows 2008). What we have done in the past is to create a test machine using a virtual machine. The virtual machine can then be set up to exactly mimic the new server you want to move your system to. To create a virtual machine you can use VMWare, Hyper-V or VirtualBox. You can then move your application on to the VM and test it completely. You can then document any issues you might come across and how to solve them. When you are ready to move the application to the live server, you can do so with ease by following your installation manual.

    I hope that this answers your question. Good luck!


    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer. This helps us build a healthy and positive community. Happy programming!

    • Marked as answer by Jyos Monday, April 23, 2012 9:55 PM
    Monday, April 23, 2012 9:08 PM

All replies

  • Hi Jyos

    If you have a Windows Forms Application setup, you will need to rebuild the application for 64 bit PC. But I presume you have a Web Application. Might I make a suggestion. There are many things that can go wrong, especially if you have such a big migration (Windows 2003 to Windows 2008). What we have done in the past is to create a test machine using a virtual machine. The virtual machine can then be set up to exactly mimic the new server you want to move your system to. To create a virtual machine you can use VMWare, Hyper-V or VirtualBox. You can then move your application on to the VM and test it completely. You can then document any issues you might come across and how to solve them. When you are ready to move the application to the live server, you can do so with ease by following your installation manual.

    I hope that this answers your question. Good luck!


    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer. This helps us build a healthy and positive community. Happy programming!

    • Marked as answer by Jyos Monday, April 23, 2012 9:55 PM
    Monday, April 23, 2012 9:08 PM
  • If the application was written to target .NET Framework 1.1, you will need to install .NET Framework 1.1 on the new server to get it to run as-is.

    As DirkStrauss mentioned, you can upgrade the original solution (if you have it) in either VS 2008 or VS 2010 to target .NET Framework 3.5 so the new version will run on the new server as configured. Both newer VS versions have an Upgrade Wizard that will (semi)automatically convert your old solution to the new VS format and allow you to target .NET 3.5. Of course, if issues arise, they will have to be manually corrected by a developer.

    If you plan on installing 1.1 on your new server, you should read through these threads:

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/614edf55-4cdf-4d6a-bfff-0d803ec60041

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

    Before you select this option, you should be aware of .NET Framework 1.1 end of support dates:

    http://support.microsoft.com/lifecycle/?p1=1249

    • Marked as answer by Jyos Monday, April 23, 2012 9:55 PM
    Monday, April 23, 2012 9:25 PM
  • Thank you so much to both DirkStrauss and pvdg42 for your quick answer. These are really helpful info.
    Monday, April 23, 2012 9:57 PM