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
Auto generated AssemblyFile location causes issues with symbols #146
Comments
@SimonCropp got any ideas? |
Oh, my guess as to the location of the file isn't the issue either. I changed the code to generate it in obj like everything else, and it still doesn't work. |
@wasabii how is the source nuget package generated? where does it pull files from? |
I'm having this issue just now in SharpRaven, which uses GitVersionTask. If you have an account there, you can inspect the problem on CodeBetter's TeamCity Server.
The NuGet package is generated with the following command:
And published to nuget.org with the following command:
Perhaps |
@SimonCropp @JakeGinnivan Instead of having GitVersionTask generate a new, randomly named file, can't it insert (and then, after compile, remove) the |
This is kind of a weird indirect issue, that takes some explanation.
When using GitFlowVersionTask in a project that gets packaged using NuGet into a symbols.nupkg file, and uploaded or pushed to a symbol server (such as SymbolSource.org), the GitFlowVersionTask causes an issue.
I get an error message like this:
I suspect the issue is that the temporary file is generated in AppData\Local, instead of in obj/Release. I'm imagining the are parts of the MSBuild process which generate the .pdb file, but somehow excludes things.
Or something. I don't know. Either way, GitFlowVersionTask is the only thing causing this issue. If I remove it, everything else is fine, even the other autogenerated files in obj.
The text was updated successfully, but these errors were encountered: