Upgrade to more SDK-style and latest NuGetizer - #15
Conversation
Sorry, something went wrong.
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. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
|
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. msbuild /t:restore && msbuild /t:build;pack). But VS 15.2 will work if you pass a dummy value via a property or envvar, named NuGetBuildTasksPackTarget, as noted in the friendly error message. |
Sorry, something went wrong.
Changes include:
in NuGetizer (<PackageFile Kind=Dependency Id=_._)
where it's broken right now (see Building a new enlistment fails NuGet/Home#5300)