Home: NuGetizer - Support for Visual Studio 2019

[daveylad]

Will this extension be updated to support VS2019 ?

Tried running the the installer and although VS2019 is displayed as an option it is greyed out an not selectable. The message displayed next to the option is "The extension cannot be installed into this product due to prerequisites that cannot be resolved"

[nkolev92]

//cc @kzu

[daveylad]

is anyone looking at this or is it dead in the water ? @nkolev92 @kzu

[nkolev92]

@kzu would have info on that.

I'm on the NuGet.Client team, only the issues repo is shared.

[derekwheeler-tylertech]

Is this still in limbo? Microsoft has started to let support for VS 2017 fall behind. (Specifically it no longer supports doing remote xamarin builds to a Mac that runs XCode 11). So we're forced to use VS 2019. And now we can't produce our nugets so we're basically dead. So anyway this could be bumped up priority would be appreciated. Thanks!

[daveylad]

I'd say the lack of a single response on this thread from @kzu speaks volumes in itself.

[zspitz]

Considering that the SDK project format allows embedding NuGet package details inside the project file, are there still any use case for NuGetizer 3000?

[daveylad]

Considering that the SDK project format allows embedding NuGet package details inside the project file, are there still any use case for NuGetizer 3000?

But if you're unfamiliar with the SDK project and completely familiar with NuGetizer 3000 then that's a use case right there.

[brandonchastain]

I was looking around and found this documentation on the MSBuild pack target. It looks like msbuild supports generating packages out of the box now?

[nkolev92]

@brandonchastain

You are correct, that's been around since Visual Studio 2017.
SDK based projects support it out of the box.
Old style csproj projects with PackageReference work by installing the Pack SDK. https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package-msbuild