diff --git a/docs/standard/microservices-architecture/net-core-net-framework-containers/net-framework-container-scenarios.md b/docs/standard/microservices-architecture/net-core-net-framework-containers/net-framework-container-scenarios.md index 6d95d99b28d1a..c82efd04b098d 100644 --- a/docs/standard/microservices-architecture/net-core-net-framework-containers/net-framework-container-scenarios.md +++ b/docs/standard/microservices-architecture/net-core-net-framework-containers/net-framework-container-scenarios.md @@ -17,9 +17,9 @@ In most cases for this scenario, you will not need to migrate your existing appl ## Using third-party .NET libraries or NuGet packages not available for .NET Core -Third-party libraries are quickly embracing the [.NET Standard](https://docs.microsoft.com/dotnet/articles/standard/library), which enables code sharing across all .NET flavors, including .NET Core. With the .NET Standard Library 2.0 and beyond the API surface compatibility across different frameworks has become significantly larger and in .NET Core 2.x applications can also directly reference existing .NET Framework libraries (see [compat shim](https://github.com/dotnet/standard/blob/master/docs/netstandard-20/README.md#net-framework-461-supporting-net-standard-20)). +Third-party libraries are quickly embracing the [.NET Standard](../../net-standard.md), which enables code sharing across all .NET flavors, including .NET Core. With the .NET Standard Library 2.0 and beyond the API surface compatibility across different frameworks has become significantly larger and in .NET Core 2.x applications can also directly reference existing .NET Framework libraries (see [compat shim](https://github.com/dotnet/standard/blob/master/docs/netstandard-20/README.md#net-framework-461-supporting-net-standard-20)). -In addition, the [Windows Compatibility Pack](https://docs.microsoft.com/dotnet/core/porting/windows-compat-pack) was released on NOV-2017 to extend the API surface available for .NET Standard 2.0 on Windows. This pack allows recompiling most existing code to .NET Standard 2.x with little or no modification, to run on Windows. +In addition, the [Windows Compatibility Pack](../../../core/porting/windows-compat-pack.md) was released on NOV-2017 to extend the API surface available for .NET Standard 2.0 on Windows. This pack allows recompiling most existing code to .NET Standard 2.x with little or no modification, to run on Windows. However, even with that exceptional progression since .NET Standard 2.0 and .NET Core 2.1, there might be cases where certain NuGet packages need Windows to run and might not support .NET Core. If those packages are critical for your application, then you will need to use .NET Framework on Windows Containers. @@ -31,7 +31,7 @@ The following list shows most of the technologies that are not available in .NET - ASP.NET Web Forms. This technology is only available on .NET Framework. Currently there are no plans to bring ASP.NET Web Forms to .NET Core. -- WCF services. Even when a [WCF-Client library](https://github.com/dotnet/wcf) is available to consume WCF services from .NET Core, as of mid-2017, the WCF server implementation is only available on .NET Framework. This scenario might be considered for future releases of .NET Core, there are even some APIs considered for inclusion in the [Windows Compatibility Pack](https://docs.microsoft.com/dotnet/core/porting/windows-compat-pack). +- WCF services. Even when a [WCF-Client library](https://github.com/dotnet/wcf) is available to consume WCF services from .NET Core, as of mid-2017, the WCF server implementation is only available on .NET Framework. This scenario might be considered for future releases of .NET Core, there are even some APIs considered for inclusion in the [Windows Compatibility Pack](../../../core/porting/windows-compat-pack.md). - Workflow-related services. Windows Workflow Foundation (WF), Workflow Services (WCF + WF in a single service), and WCF Data Services (formerly known as ADO.NET Data Services) are only available on .NET Framework. There are currently no plans to bring them to .NET Core. @@ -48,16 +48,16 @@ In the meantime, if any platform or service in Azure still doesn't support .NET ### Additional resources - **.NET Core Guide** - [https://docs.microsoft.com/dotnet/articles/core/index](https://docs.microsoft.com/dotnet/articles/core/index) + [https://docs.microsoft.com/dotnet/core/index](../../../core/index.md) - **Porting from .NET Framework to .NET Core** - [https://docs.microsoft.com/dotnet/articles/core/porting/index](https://docs.microsoft.com/dotnet/articles/core/porting/index) + [https://docs.microsoft.com/dotnet/core/porting/index](../../../core/porting/index.md) - **.NET Framework on Docker Guide** - [https://docs.microsoft.com/dotnet/articles/framework/docker/](https://docs.microsoft.com/dotnet/articles/framework/docker/) + [https://docs.microsoft.com/dotnet/framework/docker/](../../../framework/docker/index.md) - **.NET Components Overview** - [*https://docs.microsoft.com/dotnet/standard/components*](../../components.md) + [https://docs.microsoft.com/dotnet/standard/components](../../components.md)