📎 AI Summary:
The thread discusses upgrading a Windows Server from 2003 to 2016 and its impact on existing .NET web applications developed with Visual Studio 2010. The first poster questions whether Visual Studio 2010 needs to be upgraded to ensure compatibility with Server 2016, while a response clarifies that IDE version isn't the main concern; instead, the focus should be on the target .NET framework version, which affects compatibility. The overall advice emphasizes that older applications may still run on newer servers but should be updated to avoid end-of-life issues, and upgrading Visual Studio may involve code adjustments if targeting newer frameworks.

jkanna86

New Member
Joined
Jan 5, 2018
Messages
1
Thread Author #1
We are planning to upgrade our windows server from 2003 to 2016.
In our existing windows server 2003 we hosted dotnet webservers and its running on visual studion 2010.
If we upgrade server from 2003 to 2016, is this required to upgrade my visual studio application from 2010 to higher version or the same version VS2010 will perform without any disturbances in server 2016 or higher versions.
 

Solution
Well visual studios is just the IDE and doesn't really dictate the compatibility of your developed code. That will be determined by which .NET framework you target in the project. Older .NET applications should still run on server 2016, but it's always a good idea to update your code base as the older ones will be come EOL. Changing the target framework can result in some code redesign/rewrites as methods change from framework to framework. VS2010 itself is an EOL product as of 2 years ago.

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
Well visual studios is just the IDE and doesn't really dictate the compatibility of your developed code. That will be determined by which .NET framework you target in the project. Older .NET applications should still run on server 2016, but it's always a good idea to update your code base as the older ones will be come EOL. Changing the target framework can result in some code redesign/rewrites as methods change from framework to framework. VS2010 itself is an EOL product as of 2 years ago.
 

Solution