-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New versions not being published to NuGet? #9
Comments
@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")] |
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]/") |
@ArcanoxDragon another workaround is to import the |
@madskristensen - Thoughts? |
Doing a new release now |
It looks like the AppVeyor builds are not successfully publishing new NuGet packages. I need to use a newer version of
Community.VisualStudio.Toolkit
than17.0.430
because of this issue, but it seems theCommunity.VisualStudio.Toolkit.DependencyInjection.Core
package fails on any version newer than 430 (even with aProvideBindingRedirect
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.The text was updated successfully, but these errors were encountered: