Skip to content

fix broken link #1166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 22, 2016
Merged

fix broken link #1166

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b819136
fix broken link
mairaw Oct 21, 2016
3cadd81
fixed another broken link
mairaw Oct 21, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/core/porting/libraries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,7 +257,7 @@ And that's it! Because your projects now target .NET Framework 4.6.2, you can u

The next step is to run the API Portability Analyzer (ApiPort) to generate a portability report that you can begin to analyze.

You'll need to make sure you understand the [API Portability tool (ApiPort)](https://github.com/Microsoft/dotnet-apiport/blob/master/docs/HowTo/Introduction.md) and can generate portability reports for targeting .NET Core. How you do this will likely vary based on your needs and personal tastes. What follows are a few different approaches - you may find yourself mixing each approach depending on how your code is structured.
You'll need to make sure you understand the [API Portability tool (ApiPort)](https://github.com/Microsoft/dotnet-apiport/blob/master/docs/HowTo/) and can generate portability reports for targeting .NET Core. How you do this will likely vary based on your needs and personal tastes. What follows are a few different approaches - you may find yourself mixing each approach depending on how your code is structured.

### Dealing Primarily with the Compiler

Expand Down
4 changes: 2 additions & 2 deletions docs/core/porting/third-party-deps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,8 +87,8 @@ The .NET Team would like to know which libraries are the most important to suppo

## Analyzing Dependencies which aren't NuGet Packages

You may have a dependency that isn't a NuGet package, such as a DLL in the filesystem. The only way to determine the portability of that dependency is to run the [ApiPort tool](https://github.com/Microsoft/dotnet-apiport/blob/master/docs/HowTo/Introduction.md).
You may have a dependency that isn't a NuGet package, such as a DLL in the filesystem. The only way to determine the portability of that dependency is to run the [ApiPort tool](https://github.com/Microsoft/dotnet-apiport/blob/master/docs/HowTo/).

## Next steps

If you're porting a library, check out [Porting your Libraries](libraries.md).
If you're porting a library, check out [Porting your Libraries](libraries.md).