Upgrade to more SDK-style and latest NuGetizer #15
Conversation
This file contains 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
Changes include: - Adding the empty dependency groups via the built-in supported mechanism in NuGetizer (`<PackageFile Kind=Dependency Id=_._`) - Replacing usage of packages.config for PackageReference in both projects - Adding NuGet restore workaround for VS2017 Version 15.3.0 Preview 2.0 [26530.1.d15rel] where it's broken right now (see NuGet/Home#5300)
|
FWIW, I tried the resulting nuget package on iOS and Android apps and no prompts were raised. |
|
Hello! Just wanted to confirm: this works with the released products right now? I would not want to rely on the upcoming preview for it. |
|
As almost always, it depends ;). Users can use any VS that supports the NETStandard you're producing, just like the previous hardcoded nuspec had. building the nuget package requires VS 15.3 to "just work" (i.e. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes include:
in NuGetizer (
<PackageFile Kind=Dependency Id=_._)where it's broken right now (see Building a new enlistment fails NuGet/Home#5300)