[Mono-devel-list] GAC (design) issues

[Jaroslaw Kowalski]

No. In MS you don't have to specify a path in 2 cases:

1. For assemblies located in the same directory as csc.exe (that is for
example \WINDOWS\Microsoft.NET\Framework\v1.1.4322)
2. For assemblies located in the current directory

GAC is not on the list. See for yourself by GAC-ing your own assembly (not
the system one, as they are also found by the first rule) and compiling
something referencing that assembly.

Jarek
----- Original Message ----- 
From: "Andy Satori" <dru at druware.com>
To: "Todd Berman" <tberman at sevenl.net>
Cc: <mono-devel-list at lists.ximian.com>; "Jaroslaw Kowalski"
<jaak at zd.com.pl>; "Gert Driesen" <gert.driesen at pandora.be>; "Ian MacLean"
<ianm at ActiveState.com>; "Miguel de Icaza" <miguel at novell.com>; "Jackson
Harper" <jackson at ximian.com>
Sent: Sunday, May 02, 2004 3:28 PM
Subject: Re: [Mono-devel-list] GAC (design) issues


>
> On May 1, 2004, at 4:22 AM, Todd Berman wrote:
>
> > Allright, ill bite. comments/questions inline.
> >
> > On Sat, 2004-01-05 at 10:02 +0200, Jaroslaw Kowalski wrote:
> >> +1 to Ian and Gert. We all suffer from NAnt not working on Linux.
> >> Fixing
> >> nant to deal with the current mono behaviour would be a major hack,
> >> because
> >> you can no longer specify system assemblies references in a portable
> >> manner.
> >>
> >
> > How exactly do you do this on ms.net? by setting up your path properly?
> > that sounds like the original hack.
> >
>
> In the MS Implementation, if it's in the GAC, you don't specify a path.
>
> Andy
>