V11#558
Open
joeloff wants to merge 2 commits into
Open
Conversation
| <PropertyGroup> | ||
| <!-- This avoids creating VS.*.symbols.nupkg packages that are identical to the original package. --> | ||
| <AutoGenerateSymbolPackages>false</AutoGenerateSymbolPackages> | ||
| <ProducesDotNetReleaseShippingAssets>true</ProducesDotNetReleaseShippingAssets> |
Member
There was a problem hiding this comment.
This will affect all packages being produced. Is it possible to fine-tune the list of what gets published to nuget.org?
Member
Author
There was a problem hiding this comment.
Can't we just turn off "shipping" for the rest or do we want shipping packages that don't go to nuget.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix the versioning for Microsoft.Deployment.DotNet.Releases. Currently, active release branches are all producing some form of a 2.0.0 prerelease package, none of which ship on NuGet. This is causing problems for the VMR when some 2.0.0 packages land on the wrong feed.
Starting with 10.0 and 11.0, we'll produce versioned packages that will flow to the SDK and into other products like Visual Studio (this happens as part of the template locator from the SDK that's inserted into Visual Studio).