From 342c375d23ad185cca3c2327ee9b2046ff07b961 Mon Sep 17 00:00:00 2001 From: Michael Friis Date: Fri, 21 Oct 2016 07:20:07 -0700 Subject: [PATCH] fix link --- docs/core/porting/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/porting/index.md b/docs/core/porting/index.md index fd116a2381687..9cf41f99df501 100644 --- a/docs/core/porting/index.md +++ b/docs/core/porting/index.md @@ -28,7 +28,7 @@ The recommended process for porting follows the following series of steps. Each This ensures that you can use API alternatives for .NET Framework-specific targets in the cases where .NET Core can't support a particular API. -3. Use the [API Portability Analyzer tool](https://github.com/Microsoft/dotnet-apiport/blob/master/docs/HowTo/Introduction.md) to analyze your assemblies and develop a plan to port based on its results. +3. Use the [API Portability Analyzer tool](https://github.com/Microsoft/dotnet-apiport/blob/master/docs/HowTo) to analyze your assemblies and develop a plan to port based on its results. The API Portability Analyzer tool will analyze your compiled assemblies and generate a report which shows a high-level portability summary and a breakdown of each API you're using that isn't available on .NET Core. You can use this report alongside an analysis of your codebase to develop a plan for how you'll port your code over.