[PR] The proj files have been updated to enable SourceLink

[JTOne123]

CSProj files have been updated to enable SourceLink in your nuget

[This pull request was created with an automated workflow]

I noticed that your repository and Nuget package are important for our .NET community, but you still haven't enabled SourceLink.

We have to take 2 steps:

1. Please approve this pull request and make .NET a better place for .NET developers and their debugging.
2. Then just upload the .snupkg file to https://www.nuget.org/ (now you can find the snupkg file along with the .nuget file)

You can find more information about SourceLine at the following links
https://github.com/dotnet/sourcelink
https://www.hanselman.com/blog/ExploringNETCoresSourceLinkSteppingIntoTheSourceCodeOfNuGetPackagesYouDontOwn.aspx

If you are interesting about this automated workflow and how it works
https://github.com/JTOne123/GitHubMassUpdater

If you notice any flaws, please comment and I will try to make fixes manually

[mcintyre321]

Then just upload the .snupkg file to https://www.nuget.org/ (now you can find the snupkg file along with the .nuget file)

Does this need to be done on every publish? As a second publish?

[JTOne123]

Please upload them together every time

[mcintyre321]

I use appveyor's nuget 'Environment' deploy feature, not sure it supports it yet :| Also, I wonder if OneOf's unusual source files might cause some issues in IDE's...

…

On Thu, 25 Jun 2020 at 13:07, Pavlo Datsiuk ***@***.***> wrote: Please upload them together every time — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACDJ6SGEXI7L5ZBNSRSSGDRYM4WZANCNFSM4OIGJS5A> .

[JTOne123]

maybe they will support it in the future

But it does break nothing in your nuget right now...