-
Notifications
You must be signed in to change notification settings - Fork 80
Embed source files that do not belong to the git repo #115
Comments
csc task/command line:
|
@tmat that switch approach works if your code generators participate and prepare the msbuild items before the compiler is invoked. Does the Csc task accept a parameter for this, and do the msbuild C# targets pass that parameter in from an item list already? For the person building the PDB, I guess post-compilation adding source files to it is possible, but perhaps we can settle on unadvisable if there is a preferred path which is the above approach. But I'd love to learn how to do that. |
Also, what is this |
@(EmbeddedFiles) get passed to /embed |
@AArnott Yes, it does. dotnet/roslyn#12759 |
Just pointing out again (see also dotnet/roslyn#15256 (comment)) that The design for embedded source accounted for Windows PDBs as well, but due to some funding changes, the testing was not completed for VS 2017 RC. Getting it to work with Windows PDBs is tracked by dotnet/roslyn#13707, which is pushed out passed VS 2017 RTM. dotnet/roslyn#13138 has a code complete implementation of /embed working for Windows PDBs if you want to play with it sooner. |
Can you educate me on the downside to that? What prevents everyone from compiling portable pdb's? Is it that only certain debuggers support them? Which ones? |
A bit late to join the party, but this is for after the changes by @AArnott , right? |
That's how I'm seeing it, yes. |
When the build itself generates code, that code won't be in the git repo but may still be valuable to step through. This code can be embedded in the PDB such that (a future version of) the VS debugger can display it.
@tmat: any pointers to docs on how we can add sources files to the PDB?
Project owners: I'm willing to fix this.
The text was updated successfully, but these errors were encountered: