-
Notifications
You must be signed in to change notification settings - Fork 124
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
Adding the appropriate SourceLink Nuget causes build to fail #193
Comments
Could you try to run |
Pretty big log, if you want the whole thing let me know. Here's the last bit with the error, looks the same:
|
Yes, the whole file is needed for investigation. Thanks. |
Gotcha, here it is: |
Sorry, I meant the file |
Ah, I see. Emailed the file to you with the subject "Sourcelink Issue #193 binlog". Thanks! |
This is a bug in VB compiler: dotnet/roslyn#30586 The workaround is to remove <EmbedUntrackedSources>true</EmbedUntrackedSources> That is, not use the SourceLink feature that embeds untracked files automatically. |
Thanks tmat, removing |
Glad to hear that. Thanks for reporting the issue. |
The compiler issue has been fixed: dotnet/roslyn#32015 |
I've been following the documentation on this repo to enable SourceLink in an effort to be able to debug private nuget packages hosted on our Azure DevOps account, but have run into an issue.
The mere act of installing the appropriate nuget package (Microsoft.SourceLink.Vsts.Git) causes the build to fail with the following error:
1>vbc : error BC2001: file 'C:\Users\USER\AppData\Local\Temp\.NETStandard' could not be found
1>vbc : error BC2001: file 'C:\Projects\TheApp\TheLibrary\TheLibrary\Version=v2.0.AssemblyAttributes.vb' could not be found
This makes me think I'm missing some SDK or have the wrong version of VS2017, but it all seems ok: I'm on VS2017 15.8.7 (Pro), have the .NET Core SDK 2.1.403 installed and the project is a .NET Standard 2.0 library.
Removing the nuget package makes the build pass again, but obviously removes the SourceLink support as well.
The text was updated successfully, but these errors were encountered: