Because the tool uses dotnet pack to create the symbol packages, it does not support the kinds of project types, that need additonal MSBuild targets.
For example, you cannot debugify a project that uses MsBuild.Sdks.Extras in order to have a multi-platform nuget targeting iOS, UWP and Android.
In such cases, we need to fallback to using msbuild.exe directly.
There is a tool which ships with Visual Studio since 2017: vswhere
It can easily be found by resolving an environment variable https://github.com/Microsoft/vswhere
Because the tool uses
dotnet pack
to create the symbol packages, it does not support the kinds of project types, that need additonal MSBuild targets.For example, you cannot debugify a project that uses
MsBuild.Sdks.Extras
in order to have a multi-platform nuget targeting iOS, UWP and Android.In such cases, we need to fallback to using msbuild.exe directly.
There is a tool which ships with Visual Studio since 2017: vswhere It can easily be found by resolving an environment variable
https://github.com/Microsoft/vswhere
Then, it can be used to return the path to msbuild.exe The example can be found here
dotnet pack
fails, fallback to using msbuild.exe to create the symbol nuget packages that can then be debugified!