- Microsoft office compatibility pack mac os x how to#
- Microsoft office compatibility pack mac os x code#
- Microsoft office compatibility pack mac os x series#
Microsoft office compatibility pack mac os x code#
Verify the code is running on Windows. We recommend you to use RuntimeInformation.IsOSPlatform() for platform checks: This allows you to write code that calls Windows-only APIs after doing a platform check at runtime, rather than having to use conditional compilation using #if. Your code can always assume that all the APIs exist across all platforms, but if they are Windows-only they throw PlatformNotSupportedException.
However, if you plan to migrate your application to Linux or macOS, you need to take the platform support into account.Īs you can see in the previous table, about half of the components in the Windows Compatibility Pack are Windows-only, the other half works on any platform. 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. Migrate to ASP.NET Core (while still targeting the.If you’re planning to migrate an ASP.NET MVC application running on a local Windows server to an ASP.NET Core application running on Linux in Azure, we’d recommend you perform these steps:
Microsoft office compatibility pack mac os x series#
We highly recommend that you plan your migrations as a series of steps instead of assuming you can port the existing code base all at once.
Microsoft office compatibility pack mac os x how to#
Take a look at our documentation for more details on how to choose between.
NET Framework is the best choice for you. If you’re building Windows desktop applications, then the. NET Core is optimized for building highly scalable web applications, running on Windows, macOS or Linux. NET implementation isn’t a good enough reason (unless you’re a True Fan). But before you start porting, you should understand what you want to accomplish with the migration. This package is meant for developers that need to port existing. 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.