Hey Jo, I agree entirely with your basic point about using NuGet for the framework.
However, regarding > we try to avoid packaging libraries we don't use in applications ...the nunit framework is one such library. Charlie On Thu, 3 Dec 2015 12:50:40 +0000 Jo Shields <[email protected]> wrote: > On Wed, 02 Dec 2015 10:45:14 -0500 Chris Capon <[email protected]> wrote: > > Package: libnunit-framework2.6.3-cil > > Version: 2.6.3+dfsg-1 > > Severity: wishlist > > > > Dear Maintainer, > > > > When a .NET project that references the nunit.framework is compiled, the > > specific version number, culture and public key token are built in to the > > application. > > > > If that specific version is not found in the GAC when the application > is run, > > it will fail. > > > > When considering source code portability between systems, projects that > > reference specific versions of the nunit.framework can also not be > compiled if > > that version is not found. > > > > Under Windows, it is possible to have many different versions of NUnit > > installed concurrently in the GAC by installing from the many packages > > available on NUnit.org download site. > > > > With Debian (Testing), only the latest version is provided (currently > 2.6.3). > > This places a requirement on all .NET applications to be compiled > with the same > > nunit.framework reference. In addition, that reference must be > updated with > > each major release of the framework. > > > > Since different applications may reference different versions of the > > nunit.framework, it should be possible to install multiple versions > of the > > nunit.framework. > > > > Would it be possible to provide an installation package for each of the > > historical versions of the NUnit framework in addition to the most > current? > > This way package references do not need to be changed unnecessarily. > > > > It is also significant that these historical versions must all register > > references in the GAC which are compatible with their matching > releases on > > NUnit.org. > > This is actually a huge amount of work. In the general case, I'd suggest > using NuGet for including NUnit in your own projects, rather than > relying on what's in the distribution - we cannot rely on internet > connectivity when building packages, so need to have packages, but we > try to avoid packaging libraries we don't use in applications, and > multiple parallel versions of NUnit would certainly come under that heading. > >
