publishing prior minor version updates

Topics: Ecosystem
Jan 28, 2013 at 1:41 AM

I have a package targeting asp.net net40 projects with version 1.6.0.* where I want to create release branch of those sources and then start work on port of them targeting asp.net net45 with version 1.6.5.*.

If I later have to apply minor fixes to the release branch containing package targeting asp.net 40 projects will the nuget gallery allow me to publish newer 1.6.0.* drops after having published a 1.6.5.* drop?

For example lets set my asp.net net40 package is considered done at 1.6.0.1 and I then publish my first asp.net net45 package drop with same name but version number 1.6.5.0.   Can I later come along and publish a 1.6.0.2 and a 1.6.5.1 or will nuget gallery only allow the latter version number?

Developer
Jan 28, 2013 at 2:00 AM

Yes, the gallery allows you to publish packages in any version.

Jan 28, 2013 at 2:40 AM

That is great news as this gives me a way to move package output to targeting vNext web, phone and winrt framework environments while giving me a set of version numbers for use to do an bug fix update releases of the package versions that last supported targeting vPrev web, phone and winrt framework environments.

It would appear the only thing the gallery prevents is publishing packages with the same version.

Feb 10, 2013 at 5:53 AM
Hello,

It such a great topic and a good news for me...thanks for sharing...

pregnancy yoga classes online