Visualstudio-docs: Step 4 is useless with package references

[dotMorten]

Step 4 states:

> 4. You can now run the VSIXSignTool from the project's local packages location

This is a horrible solution. There's no good way to know that location, and it would change with each version. Instead there are two options this package should expose:

1. Create a dotnet tool we can just install.
2. Add a .targets file that declares a variable with the path, or a task we can just execute.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6cf20479-c8a0-eb31-45f8-3599c759b4d6
• Version Independent ID: f9ca0232-6aa0-543b-2b37-6685e69cfdb9
• Content: Signing VSIX Packages - Visual Studio
• Content Source: docs/extensibility/signing-vsix-packages.md
• Product: visual-studio-windows
• Technology: vs-ide-sdk
• GitHub Login: @madskristensen
• Microsoft Alias: madsk

[WilliamAntonRohm]

@dotMorten -- Morten, it looks like you have product feedback rather than documentation feedback. If you are looking for functionality that isn’t currently provided by the product, please use our “Suggest a feature” option in the Visual Studio Developer Community. We’d be happy to have this on record, where others can view it and upvote it, too. For more information about this works in the dev community, see our Suggest a feature page.​

[dotMorten]

@WilliamAntonRohm Well yes and no. The documentation as-is right now does not help. It doesn't actually describe how to use this tool, other than hint at that you somehow have to guess some obscure path to the tool. That needs to be addressed.
Longer-term, yes it would be good to improve the nuget package so that writing this doc would be greatly simplified.

[GF-Huang]

@dotMorten Hello, do you find any solutions for PackageReferences project ?

[GF-Huang]

Try this one guys, https://github.com/vcsjones/OpenOpcSignTool