From time to time I’ve a task to upgrade .NET projects to newer .NET Framework version. What are the benefits of raising project to a newer version?
- Improve libraries or applications overall perfomance;
- Probablly less virtual memory consumption;
- Probablly less CPU consumption;
- Latest known bugs fixes;
- Greater stability, reliability, security;
- Support newer tools and the .NET community projects in general;
- Support newer .NET framework features;
- Support higher C# version;
- Keeping projects attractive for developers.
In MSDN you can find very useful article how to determine which .NET Framework versions is installed on server or PC. In many cases, upgrade is not painful for project which is left behind only for 1 version back. Keep in mind, that .NET Framework breaking changes are published openly, you can google for them easilly. In my experience, most of the time, updates are not painful and if you need any help I’m willing to help you or your company. I personally recommend to upgrade to a newer major .NET release only after 3-6 months and to a minor release as soon as possible. Let’s be ahead of Microsoft .NET technology together.
- How to: Determine Which .NET Framework Versions Are Installed
- Moving to the .NET Framework 4.5.2
- Why you should upgrade to .NET 3.5
- Why not upgrade to the latest .NET framework?
- Why do projects opt to stay on an older version of the .NET Framework?
- Why Should I Upgrade from .Net Framework 3.5 to .Net Framework 4 ? (Navneet Gupta)