New versions not being published to NuGet?

VsixCommunity / Community.VisualStudio.Toolkit.DependencyInjection

Adds Dependency Injection tooling for the Community.VisualStudio.Toolkit

Other

14 stars 7 forks source link

New versions not being published to NuGet? #9

Open ArcanoxDragon opened 1 year ago

ArcanoxDragon commented 1 year ago

It looks like the AppVeyor builds are not successfully publishing new NuGet packages. I need to use a newer version of Community.VisualStudio.Toolkit than 17.0.430 because of this issue, but it seems the Community.VisualStudio.Toolkit.DependencyInjection.Core package fails on any version newer than 430 (even with a ProvideBindingRedirect attribute on my VSIX assembly redirecting it to a newer version).

The update of Community.VisualStudio.Toolkit merged via #8 hasn't made it to a new NuGet package version yet.

AlonAm commented 1 year ago

@ArcanoxDragon As a workaround, you can add this redirection to the AssemblyInfo.cs file

[assembly: ProvideBindingRedirection(AssemblyName = "Community.VisualStudio.Toolkit", OldVersionLowerBound = "17.0.430.0")]

AlonAm commented 11 months ago

AppVeyor Build Log: "NuGet" deployment has been skipped as environment variable has not matched ("appveyor_repo_commit_message_extended" is "Update DIToolkitPackage.cs", should be "/[release]/")

AlonAm commented 11 months ago

@ArcanoxDragon another workaround is to import the Community.VisualStudio.Toolkit.DependencyInjection.Core project to your solution

StevenRasmussen commented 10 months ago

@madskristensen - Thoughts?

madskristensen commented 10 months ago

Doing a new release now