Check the resulting EXE it should contain the correct case, regardless of the compiler switches.
Piers.
> -----Original Message-----
> From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 08, 2003 4:27 PM
> To: Juli Mallett
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Mono-list] VFAT vs Unix filesystems...
>
>
> That makes a total of my 6 cents. I promise there'll be no
> more "donations".
>
> > > I think that the best thing one can do is to ignore the
> problem and
> force
> > > application developers to write their code using correct case for
> > > dll
> names.
> >
> > Yeah, that's going to happen. Serious momentum issues there.
>
> Really? I think that System.Xml vs System.XML is the only big
> problem right now. Many projects reference it, some do it one
> way, some do it another way.
>
> In MS GAC there is System.Xml.dll, mono has System.Xml.dll,
> but if you look inside of any .csproj file, you'll get:
>
> <Reference
> Name = "System.XML"
> AssemblyName = "System.Xml"
> HintPath =
> "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\System.XML.dll"
> />
>
> Really cool, isn't it? I don't believe in conspiracy theory,
> but some could say that MS is locking you in to using windows
> by introducing this kind of ambiguity which cannot be
> resolved under Unix/Linux.
>
> Beside System.Xml I haven't seen any other library name
> misspelled yet.
>
> Jarek
>
>
> _______________________________________________
> Mono-list maillist - [EMAIL PROTECTED]
> http://lists.ximian.com/mailman/listinfo/mono-list
>
