Skip to content

Remove the binary_analysis link in favor of upgrade-with-the-cli-tool section of .NET Upgrade Assistant tool page #41674

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.

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
Changes from all commits
Commits
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/third-party-deps.md
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ The .NET Team would like to know which libraries are the most important to suppo

## Analyze non-NuGet dependencies

You may have a dependency that isn't a NuGet package, such as a DLL in the file system. You can determine the portability of that dependency by using the [binary analysis](https://github.com/dotnet/upgrade-assistant/blob/main/docs/binary_analysis.md) functionality of the [.NET Upgrade Assistant](upgrade-assistant-overview.md).
You might have a dependency that isn't a NuGet package, such as a DLL in the file system. You can determine the portability of that dependency with the CLI version of the [.NET Upgrade Assistant](upgrade-assistant-overview.md#upgrade-with-the-cli-tool) tool.

## Next steps

Expand Down
Loading