RE: .NET Fit Deployment

Hi Ward,

The GAC is the Global Assembly Cache, a place for storing "shared"
assemblies.
To go there, they must be strongly named and can exist in multiple
side-by-side
versions.

The GAC is not to be used lightly, since it makes installation more 
complex.
Life is easier when assemblies that an app needs are simply installed 
with
it
in it's directory. Some people try to share everything across multiple 
apps
in a product line, leading to the need to update everything at once.

However, a test utility has a particular kind of sharing that's needed. 
The
test runner must have access to certain core classes and so must the 
tests:
in this case the user-written fixtures. It would be nice to be able to 
just
install fit and reference fit.dll on a "wherever it is" basis, which 
you can
do when it's in the GAC.

One difference I sense between Java and .NET - not knowing Java well I 
could
be wrong - is that it's very easy in .NET, and harder in Java, to build 
an
application against one version of a base assembly/package and end up
running
it against a different version. In Java, I think you'd have to work to 
do
that
but in .NET it just happens all the time.

This is made even more complicated in NUnit where we ended up running 
the
tests in a separate AppDomain. I think the same need could arise in 
Fitster,
if you want to change and recompile test fixtures while it's up.

Anyway, that's probably more than you wanted to know. I take it you 
guys had
not considered it, so I may experiment with it. I notice that the latest
download seems to be from back in October... is any more development 
being
done on the C# version of Fit?

Charlie

P.S.: I haven't heard any further from Francesco, have you?

> -----Original Message-----
> From: Ward Cunningham [mailto:[email protected]]
> Sent: Thursday, July 31, 2003 8:24 AM
> To: Charlie Poole
> Subject: Re: .NET Fit Deployment
>
>
>
> On Wednesday, July 30, 2003, at 11:36  AM, Charlie Poole wrote:
>
>> Needing to put the fit assemblies into every project is a bit of a
>> pain.
>>
>> In NUnit, we dealt with a similar issue by putting the framework into
>> the
>> GAC.
>> Have you found tried this? Found problems with it?
>>
>
> What is a GAC?
>
> --
> Ward Cunningham
> 503-245-5633 v	mailto:[email protected]
> 503-246-5587 f	http://c2.com
>
>

--
Ward Cunningham
503-245-5633 v	mailto:[email protected]
503-246-5587 f	http://c2.com