[Mono-list] VFAT vs Unix filesystems...
Piers Haken
piersh@friskit.com
Wed, 8 Jan 2003 20:16:58 -0800
This is a multi-part message in MIME format.
------_=_NextPart_001_01C2B795.F3D47A56
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Check the resulting EXE it should contain the correct case, regardless
of the compiler switches.
Piers.
> -----Original Message-----
> From: Jaroslaw Kowalski [mailto:jarek@atm.com.pl]=20
> Sent: Wednesday, January 08, 2003 4:27 PM
> To: Juli Mallett
> Cc: mono-list@ximian.com
> Subject: Re: [Mono-list] VFAT vs Unix filesystems...
>=20
>=20
> That makes a total of my 6 cents. I promise there'll be no=20
> more "donations".
>=20
> > > I think that the best thing one can do is to ignore the=20
> problem and
> force
> > > application developers to write their code using correct case for=20
> > > dll
> names.
> >
> > Yeah, that's going to happen. Serious momentum issues there.
>=20
> Really? I think that System.Xml vs System.XML is the only big=20
> problem right now. Many projects reference it, some do it one=20
> way, some do it another way.
>=20
> In MS GAC there is System.Xml.dll, mono has System.Xml.dll,=20
> but if you look inside of any .csproj file, you'll get:
>=20
> <Reference
> Name =3D "System.XML"
> AssemblyName =3D "System.Xml"
> HintPath =3D=20
> "..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\System.XML.dll"
> />
>=20
> Really cool, isn't it? I don't believe in conspiracy theory,=20
> but some could say that MS is locking you in to using windows=20
> by introducing this kind of ambiguity which cannot be=20
> resolved under Unix/Linux.
>=20
> Beside System.Xml I haven't seen any other library name=20
> misspelled yet.
>=20
> Jarek
>=20
>=20
> _______________________________________________
> Mono-list maillist - Mono-list@ximian.com=20
> http://lists.ximian.com/mailman/listinfo/mono-list
>=20
------_=_NextPart_001_01C2B795.F3D47A56
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>RE: [Mono-list] VFAT vs Unix filesystems...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=3D2>Check the resulting EXE it should contain the correct =
case, regardless of the compiler switches.</FONT>
</P>
<P><FONT SIZE=3D2>Piers.</FONT>
</P>
<P><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: Jaroslaw Kowalski [<A =
HREF=3D"mailto:jarek@atm.com.pl">mailto:jarek@atm.com.pl</A>] </FONT>
<BR><FONT SIZE=3D2>> Sent: Wednesday, January 08, 2003 4:27 PM</FONT>
<BR><FONT SIZE=3D2>> To: Juli Mallett</FONT>
<BR><FONT SIZE=3D2>> Cc: mono-list@ximian.com</FONT>
<BR><FONT SIZE=3D2>> Subject: Re: [Mono-list] VFAT vs Unix =
filesystems...</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> That makes a total of my 6 cents. I promise =
there'll be no </FONT>
<BR><FONT SIZE=3D2>> more "donations".</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> > > I think that the best thing one can do =
is to ignore the </FONT>
<BR><FONT SIZE=3D2>> problem and</FONT>
<BR><FONT SIZE=3D2>> force</FONT>
<BR><FONT SIZE=3D2>> > > application developers to write their =
code using correct case for </FONT>
<BR><FONT SIZE=3D2>> > > dll</FONT>
<BR><FONT SIZE=3D2>> names.</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> > Yeah, that's going to happen. Serious =
momentum issues there.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Really? I think that System.Xml vs System.XML is =
the only big </FONT>
<BR><FONT SIZE=3D2>> problem right now. Many projects reference it, =
some do it one </FONT>
<BR><FONT SIZE=3D2>> way, some do it another way.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> In MS GAC there is System.Xml.dll, mono has =
System.Xml.dll, </FONT>
<BR><FONT SIZE=3D2>> but if you look inside of any .csproj file, =
you'll get:</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT =
SIZE=3D2>> =
<Reference</FONT>
<BR><FONT =
SIZE=3D2>> =
Name =3D =
"System.XML"</FONT>
<BR><FONT =
SIZE=3D2>> =
=
AssemblyName =3D "System.Xml"</FONT>
<BR><FONT =
SIZE=3D2>> =
HintPath =
=3D </FONT>
<BR><FONT SIZE=3D2>> =
"..\..\..\WINNT\Microsoft.NET\Framework\v1.0.3705\System.XML.dll&quo=
t;</FONT>
<BR><FONT =
SIZE=3D2>> =
/></FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Really cool, isn't it? I don't believe in =
conspiracy theory, </FONT>
<BR><FONT SIZE=3D2>> but some could say that MS is locking you in to =
using windows </FONT>
<BR><FONT SIZE=3D2>> by introducing this kind of ambiguity which =
cannot be </FONT>
<BR><FONT SIZE=3D2>> resolved under Unix/Linux.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Beside System.Xml I haven't seen any other =
library name </FONT>
<BR><FONT SIZE=3D2>> misspelled yet.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Jarek</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>> Mono-list maillist - =
Mono-list@ximian.com </FONT>
<BR><FONT SIZE=3D2>> <A =
HREF=3D"http://lists.ximian.com/mailman/listinfo/mono-list">http://lists.=
ximian.com/mailman/listinfo/mono-list</A></FONT>
<BR><FONT SIZE=3D2>> </FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2B795.F3D47A56--