

NET Core application on Windows only, then you don’t have to worry about whether an API is cross-platform or not. The following table describes the APIs that are already part of the Windows Compatibility Pack or are coming in a subsequent update: Component The Windows Compatibility Pack is currently in preview because it’s still a work in progress. This maximizes the number of APIs you have at your disposal.

NET Core project, we recommend you first add the Windows Compatibility Pack by installing the NuGet package. NET Framework documentation provides more details on the recommended process and which tools you can use.īefore bringing existing. It also allows you to learn more about your code base and adjust your plans as you discover issues. This reduces the complexity and churn you have to reason about at once. The primary point is that you perform one step at a time to ensure your application stays operational along the way. For example, you might need to deploy to Azure before you perform the other migration steps. The order of steps might vary, depending on your business goals and what value you need to accomplish first.


Today, we’re happy to announce that we made it even easier with the Windows Compatibility Pack, which provides access to an additional 20,000 APIs via a single NuGet package. NET Core 2.0, we already made this much easier, thanks to. NET Core used to be quite hard because the available API set was very small.
