nunit-dev team mailing list archive

[André Nogueira <andre.nogueira@xxxxxxxxx>]

Hello,

Can there be any problems when someone is working on two projects which
use different versions of NUnit, and where both projects expect NUnit to
be in the GAC?

- André

Charlie Poole wrote:
> Hi Fabio and Everyone,
>  
> Let's discuss this. Pros? Cons?
>  
> Personally, I'm in favor. I think it makes life easier for users, some
> of whom are confused
> by the need to copy the framework to the output directory. They
> (falsely) assume that NUnit
> will find the framework for them. It also makes life easier for any
> third-party runner that needs
> to reference it.
>  
> As far as the default, I'd vote for the GAC as the only option for the
> msi install. If someone
> wants to run it from their project tree instead, they can use the
> binary zip.
>  
> Charlie
>
>     ------------------------------------------------------------------------
>     *From:* nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxxx
>     [mailto:nunit-dev-bounces+charlie=nunit.com@xxxxxxxxxxxxxxxxxxx]
>     *On Behalf Of *Fabio Maulo
>     *Sent:* Thursday, July 30, 2009 4:54 AM
>     *To:* nunit-dev@xxxxxxxxxxxxxxxxxxx
>     *Subject:* Re: [Nunit-dev] Installation layout for NUnit V3
>
>     I have only one issue about installation.
>     IMO we should have an explicit option to install the framework in
>     the GAC and the default should be "false".
>
>     2009/7/30 Andreas Schlapsi <a.schlapsi@xxxxxx
>     <mailto:a.schlapsi@xxxxxx>>
>
>         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
>         <http://nunit.com>@lists.launchpad.net
>         <http://lists.launchpad.net>
>         >> [mailto:nunit-dev-bounces+charlie
>         <mailto:nunit-dev-bounces%2Bcharlie>=nunit.com
>         <http://nunit.com>@lists.launchpad.ne <http://lists.launchpad.ne>
>         >> 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
>         <https://launchpad.net/%7Enunit-dev>
>         >> Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
>         <mailto:nunit-dev@xxxxxxxxxxxxxxxxxxx>
>         >> Unsubscribe : https://launchpad.net/~nunit-dev
>         <https://launchpad.net/%7Enunit-dev>
>         >> More help   : https://help.launchpad.net/ListHelp
>         >>
>         >
>         >
>         >
>         >
>         > _______________________________________________
>         > Mailing list: https://launchpad.net/~nunit-dev
>         <https://launchpad.net/%7Enunit-dev>
>         > Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
>         <mailto:nunit-dev@xxxxxxxxxxxxxxxxxxx>
>         > Unsubscribe : https://launchpad.net/~nunit-dev
>         <https://launchpad.net/%7Enunit-dev>
>         > More help   : https://help.launchpad.net/ListHelp
>         >
>
>
>         _______________________________________________
>         Mailing list: https://launchpad.net/~nunit-dev
>         <https://launchpad.net/%7Enunit-dev>
>         Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
>         <mailto:nunit-dev@xxxxxxxxxxxxxxxxxxx>
>         Unsubscribe : https://launchpad.net/~nunit-dev
>         <https://launchpad.net/%7Enunit-dev>
>         More help   : https://help.launchpad.net/ListHelp
>
>
>
>
>     -- 
>     Fabio Maulo
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
>