-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Allow custom compilers to inject sources into symbol packages #4639
Comments
@enricosada is this still an issue? |
no @piotrpMSFT this issue can be closed, portablepdb or pdb on windows are supported. |
I'm not saying this isn't resolved, but @enricosada when I mad this issue, it had nothing to do with portable PDBs. |
sry @Alxandr i confused empty symbol package with empty debug symbols assembly (thinking about the empty pdb generated atm by dotnet build with f#) so about symbol package: using netcore sdk preview1:
output of
and
That was the issue before @Alxandr ? |
Yes. I believe this was fixed by convention when the F# compiler started using the same fields for what files to compile as the C# compiler did. Still think it should be allowed for the compiler to inject into what goes into the symbols package, but yeah, this works. |
The team is actively working on enabling MSBuild and the component affected will be superseded by the new project system, so I am closing this issue. |
Produce Only Preprocessor Files in ProduceContentAssets
…0200624.2 (#4639) Microsoft.Build.Localization , Microsoft.Build From Version 16.7.0-preview-20323-01 -> To Version 16.7.0-preview-20324-02 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
From @Alxandr on May 30, 2015 17:58
With how my new F# compiler for DNX work, I end up with empty symbol packages. Now, symbolsource doesn't support DNX targets yet so it's not that much of a problem ^^, but I would still like for a way for my compiler to DNU what sources/additional sources to include in the symbols package.
Copied from original issue: aspnet/dnx#1995
The text was updated successfully, but these errors were encountered: