Open applejag opened 5 years ago
This happens because generating full pdbs is not supported on for .NET Core. If you are using core (dotnet), it only supports portable pdbs. If you want to generate full pdbs, I suggest using windows. I believe the same is true for mono, which is why you mentioned the property setting above. In any case, looping in @radical to make an accurate comment and guidance on mono.
Trying to use mono's pdb2mdb in a Docker container. But I'm always getting:
This has boiled down to me finding that when I use msbuild in the Docker container, it always produces portable PDB files, no-matter what I supply with either the
/p:DebugType=Full
flag on msbuild, or via the DebugType property in my.csproj
files.This only happens for me when I use the linux distribution of .NET Core SDK for Docker (2.2.104) (
mcr.microsoft.com/dotnet/core/sdk:2.2
) and not with my windows dotnet installation.I found while doing a
--verbose=Diagnostic
build (when having DebugType set in the .csproj) that this one item occurs:Why is it overriding my
DebugType
property? Why is it doing that?Steps to reproduce
Via using Docker:
Both via
dotnet build
andmsbuild
results in portable pdb. Peek at~/1/testlib.pdb
and~/2/testlib.pdb
, and see theire all portable pdbs. Not what I requested.OS info:
If applicable, version of the tool that invokes MSBuild (Visual Studio, dotnet CLI, etc):