-
Notifications
You must be signed in to change notification settings - Fork 391
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
Add SourceLink #5619
Comments
@tmat can you point me to the targests in arcade that do sourcelink? I think the easiest way forward is to copy those |
@jmarolf Is Project System official built done from an internal mirror in dnceng/devdiv? If not, you can just add a package reference to Microsoft.SourceLink.GitHub package. You don't need anything special. Is there a plan to move PS to Arcade? |
No arcade is all about shipping as part of the .NET Core SDK and has very little support for VSIXes shipping in Visual Studio. As a VS only component 90% of arcade is noise to us |
That's not quite true. We use Arcade for Interactive Window repo as well. |
This repo is using RepoToolset which is no longer maintained. Arcade SDK is. |
Does it build out of dnceng internal like arcade recommends? |
Not currently, I was about to switch to that if possible. Whether the official builds build from devdiv or dnceng is orthogonal to Arcade though. Roslyn also builds from devdiv currently. |
Alright, there is no easy path forward. The existing repotoolset targets set out-of-date properties that interfere with sourcelink. We either need to move off of repotoolset entirely or move to arcade. I'll leave this decision up to @drewnoakes and @davkean and the @dotnet/project-system team to decide |
Can you point me to this conclusion? |
@davkean pull down the branch from #5620 you will get this build error
looking at the binlog (that is in spanish? I guess we have all the binlogs written to the same place?) you can see the two sourcelink targets interact.
|
Okay thanks, I think we can handle that without throwing the baby out with the bath water. |
I suppose some careful over-ridding of targets could make things work. I will freely admit that is beyond me. Look forward to seeing the solution |
Putting this back for review since it seems the work on this was being complicated by roslyn-tools. Since we don't use roslyn-tools anymore, this is likely easier to do. Personally, I don't know anything about SourceLink though. |
@MiYanni I've set up source link for NuGet packages before so may be able to help if you wanted to pick this up. https://github.com/dotnet/sourcelink#using-source-link-in-net-projects One tip is to use NuGet Package Explorer to verify the SourceLink configuration for a .nupkg file. It will tell you if it's configured correctly, which will save a lot of time. |
yeah it's pretty much
|
Assigning this to me since this can help ramp-up in with dotnet/sdk#1458 |
Yes, please do this. Debugging this assembly from outside the team is no fun without source code. |
I've ended up figuring it out after running into an issue that Andrew actually created. dotnet/sourcelink#492 |
Microsoft.VisualStudio.ProjectSystem.Managed.dll doesn't appear to be SourceLinked. Would be super nice to add SourceLink for easier debugging.
The text was updated successfully, but these errors were encountered: