This is just a guess... it'll probably try to update everything, but it might rollback when compatible dlls are not found in the package.
You can test this by creating a local package source (pointing to a folder where you drop the nupkg files) Now, to answer your implicit question :-), we should NOT create a differently-named package for NH4. 4.0 is the currently stable .NET version, and projects using 3.5 are already in the maintenance stage, where people usually don't blindly update the libs. On Mon, Mar 18, 2013 at 2:21 PM, Oskar Berggren <[email protected]>wrote: > Does anyone know... > > If we release NHibernate 4.x under the existing "NHibernate" Nuget > package name, containing binaries only for .Net 4.0, is the Nuget > client smart enough to suggest an update only for projects that > actually target .Net 4.0? Or will it try to update also projects that > target .Net 3.5? > > /Oskar > > -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
