nunit-dev team mailing list archive

["Charlie Poole" <charlie@xxxxxxxxx>]

Hi Andreas,

Cool! I'd like to do a snapshot with it included.

Putting Framework under nunit-3.0 seems to imply that the
version numbers will be in synch. But imagine some future
user who is running the 3.0 Gui but has tests that use
the 3.0, 3.1 and 3.2 frameworks - which we released
separately as improvements were added.

Therefore, I think this should be (something like):

NUnit
  Framework
     3.0
     3.1
     3.2
  NUnit Gui
     3.0

OR

NUnitFramework
   3.0
   3.1
   3.2
NUnit 3.0

OR

NUnitFramework
   3.0
   3.1
   3.2
SomeOtherNameForTheGUI 3.0 (or 1.0?)

Any other ideas?

Charlie


> -----Original Message-----
> From: nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxxx 
> [mailto:nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxx
> t] On Behalf Of Andreas Schlapsi
> Sent: Thursday, July 30, 2009 4:48 AM
> To: 'NUnit Developer Mailing List'
> Subject: Re: [Nunit-dev] Installation layout for NUnit V3
> 
> Hi Charlie,
> 
> I created a prototype for the NUnit Framework Installer 
> yesterday. It packages the NUnit Framework for .NET 1.1 and 
> .NET 2.0 (and later for .NET 3.5 and 4.0) and suppresses all 
> variants in the feature tree without corresponding .NET 
> version installed on the target computer.
> 
> It installs the framework assemblies under <Program Files>\NUnit
> 3.0\Framework\net-1.1 or <Program Files>\NUnit 3.0\Framework\net-2.0.
> 
> What about documentation? Will the framework documentation be 
> separated?
> 
> Andreas
> 
> 
> Charlie Poole wrote:
> > Hi Andreas,
> > 
> > In breaking NUnit into multiple projects, I tried to take several 
> > things into account:
> >   * Different teams working on different projects
> >   * Independent release cycles
> >   * Possibility of third-party alternatives
> >   * Separate installation.
> > 
> > At the moment, I think we only need to decide how to install the 
> > framework, since we only have a framework project for NUnit 
> 3.0. When 
> > we add - for example - a gui project, we'll of course need 
> a separate 
> > install for that.
> > 
> > In the future, we may want to create a combined installer 
> for windows 
> > - one that bundles one or more frameworks with gui and 
> console runners 
> > and possibly other stuff. Note that this is a Windows-only problem, 
> > since linux distros have package management systems to take care of 
> > dependencies between individual packages.
> > 
> > So, for now I think the issue is how to structure the 
> installation of 
> > the framework only. This is not as simple as it sounds, since the 
> > framework is tailored to a version of .NET and there may be 
> multiple 
> > versions on a machine.
> > 
> > BTW, There will be a place on a wiki to actually post specs 
> very soon. 
> > For now we have to discuss here and/or post directly on the 
> > Whiteboard.
> > 
> > Charlie
> > 
> >> -----Original Message-----
> >> From: nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxxx
> >> [mailto:nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxx
> >> t] On Behalf Of Andreas Schlapsi
> >> Sent: Tuesday, July 28, 2009 10:07 AM
> >> To: NUnit Developer Mailing List
> >> Subject: [Nunit-dev] Installation layout for NUnit V3
> >>
> >> Hi,
> >>
> >> I'm working on the installer blueprint 
> >> (https://blueprints.launchpad.net/nunit-3.0/+spec/install-proj
> >> ect) and one of the todos is to decide on an installation 
> layout. It 
> >> should allow multiple frameworks to be installed separately from 
> >> runners like nunit-gui.
> >>
> >> Does this mean that we want separate installers for the 
> framework and 
> >> the runners? Do we need an installer for the framework? 
> The framework 
> >> assemblies are often checked in to source control.
> >>
> >> Andreas
> >>
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~nunit-dev
> >> Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~nunit-dev
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Mailing list: https://launchpad.net/~nunit-dev
> > Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~nunit-dev
> > More help   : https://help.launchpad.net/ListHelp
> > 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~nunit-dev
> Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nunit-dev
> More help   : https://help.launchpad.net/ListHelp
>