This blog post details our plans for modernizing and streamlining the ArcGIS Maps SDK for .NET at our next major release (300.0), coming in Q2 2026.
This will allow us to deliver performance improvements, to better support modern .NET development patterns, and align us more closely with Microsoft’s developer roadmap.
With that in mind, the following technologies are deprecated in ArcGIS Maps SDK for .NET 200.8:
- .NET Framework
- .NET Standard
- UWP
- x86 support on Windows (win-x86)
This means that the last version of ArcGIS Maps SDK for .NET to support these technologies is 200.8 (including all 200.8.x long-term support patch releases). ArcGIS Maps SDK for .NET 300.0 and later will not support them.
If you haven't already done so then you will need to address the following before you can upgrade to ArcGIS Maps SDK for .NET 300.0:
- If you're still building with .NET Framework, you should update your projects to use .NET 9 or later.
- If you're using UWP to build Windows apps, you should migrate to WinUI.
- If you're building 32-bit Windows apps, you should update these apps to 64-bit.
It’s important to reiterate that the 200.8 long-term support release of the ArcGIS Maps SDK for .NET will continue to support these deprecated technologies until its retirement in 2030, giving you plenty of time to update your projects if you’re not quite ready to do so now. However, in general the barriers to updating your projects are low, and we encourage you to migrate your projects away from these technologies.
Some of you may have previously assessed moving from .NET Framework to .NET, or to upgrade your 32-bit x86 Windows projects to 64-bit, but found at the time that your project dependencies might not support that move. A lot has changed in the last few years, so if you haven’t re-assessed that lately, we encourage you to take another look.
There are many great resources available that cover these migrations. Here are some handy links:
If you're still on the fence about updating from .NET Framework to .NET, now is a great time to get that done using the current 200.8 SDK.
