OK, this is now done (http://nuget.org/List/Packages/Iesi.Collections).

Since its not possible to rev a package in NuGet without also rev-ing the
version number, the new version of this is now 3.2.3002 rather than 3.2.3001
although the version of the enclosed binary is NOT a different version
(i.e., its still 3.2.3001 for the encapsulated DLL).

Happy package-consuming to all~!

Steve Bohlen
[email protected]
http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen


On Tue, Jul 26, 2011 at 8:39 AM, pvginkel <[email protected]> wrote:

> Much obliged.
>
> On Jul 26, 2:20 pm, Stephen Bohlen <[email protected]> wrote:
> > Good point.  I'll fix it shortly and post here when its done.
> >
> > Steve Bohlen
> > [email protected]http://blog.unhandled-exceptions.comhttp://
> twitter.com/sbohlen
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Jul 26, 2011 at 8:07 AM, pvginkel <[email protected]> wrote:
> > > I would like to create a JIRA issue but I'm not sure which project I
> > > should create this issue for.
> >
> > > The NuGet Iesi package I think was created by someone from the
> > > NHibernate development team has the libraries limited to Net35.
> > > However, the Iesi libraries are for .NET 2.0. For NHibernate itself
> > > this is not an issue. However, I would like to be able to use the Iesi
> > > NuGet package for other projects too, specifically a project that
> > > is .NET 2.0.
> >
> > > Is it possible that the Iesi NuGet package is updated so that it is
> > > not limited to .NET 3.5?
>

Reply via email to