[Mono-list] Windows Seup package
Gert Driesen
gert.driesen@pandora.be
Wed, 5 Mar 2003 20:36:46 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_005C_01C2E356.F0BD5DF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
Would it be possible to have the Windows Setup package register the =
following information in the registry on install :
- SdkInstallRoot (would point to the root of the mono "sdk", eg. =
c:\mono-0.20\install)
- FrameworkAssemblyDirectory (would point to the lib directory, eg. =
c:\mono-0.20\install\lib)
Each mono version should register itself (using the setup package), by =
creating a subkey (named after the version) in =
HKEY_LOCAL_MACHINE\Software\Mono and adding the two values mentioned =
above under this subkey.
For the 0.21 version, you would end up with the following registry =
entries :
HKEY_LOCAL_MACHINE\
SOFTWARE\
Mono\
0.21\
SdkInstallRoot =3D c:\mono-0.21\install
FrameworkAssemblyDirectory =3D c:\mono-0.21\install\lib
When Mono 0.22 is released and installed later on, you'd get :
HKEY_LOCAL_MACHINE\
SOFTWARE\
Mono\
0.21\
SdkInstallRoot =3D c:\mono-0.21\install
FrameworkAssemblyDirectory =3D c:\mono-0.21\install\lib
0.22\
SdkInstallRoot =3D c:\mono-0.22\install
FrameworkAssemblyDirectory =3D c:\mono-0.22\install\lib
This will allow tools (like NAnt) to discover the availability (and the =
location) of mono runtimes on Windows.
Is it also possible to include the libxml libraries (libxml2.dll and =
libxslt.dll) in the Windows Setup package ?
Thanks,
Gert
------=_NextPart_000_005C_01C2E356.F0BD5DF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.3757.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>Hi,<BR><BR>Would it be possible to have the Windows Setup package =
register=20
the following information in the registry on install :<BR><BR>- =
SdkInstallRoot=20
(would point to the root of the mono "sdk", eg.=20
c:\mono-0.20\install)<BR><BR>- FrameworkAssemblyDirectory (would =
point to=20
the lib directory, eg. c:\mono-0.20\install\lib)<BR><BR>Each mono =
version should=20
register itself (using the setup package), by creating a subkey (named =
after the=20
version) in HKEY_LOCAL_MACHINE\Software\Mono and adding the two values =
mentioned=20
above under this subkey.<BR><BR>For the 0.21 version, you would end up =
with the=20
following registry entries :<BR><BR>HKEY_LOCAL_MACHINE\<BR> =20
SOFTWARE\<BR> =20
Mono\<BR> =20
0.21\<BR> &nbs=
p; =20
SdkInstallRoot =3D=20
c:\mono-0.21\install<BR> &=
nbsp; =20
FrameworkAssemblyDirectory =3D c:\mono-0.21\install\lib<BR><BR>When Mono =
0.22 is=20
released and installed later on, you'd get=20
:<BR><BR>HKEY_LOCAL_MACHINE\<BR> =20
SOFTWARE\<BR> =20
Mono\<BR> =20
0.21\<BR> &nbs=
p; =20
SdkInstallRoot =3D=20
c:\mono-0.21\install<BR> &=
nbsp; =20
FrameworkAssemblyDirectory =3D=20
c:\mono-0.21\install\lib<BR> &nb=
sp; =20
0.22\<BR> &nbs=
p; =20
SdkInstallRoot =3D=20
c:\mono-0.22\install<BR> &=
nbsp; =20
FrameworkAssemblyDirectory =3D c:\mono-0.22\install\lib<BR><BR>This will =
allow=20
tools (like NAnt) to discover the availability (and the location) of =
mono=20
runtimes on Windows.</DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Is it also possible to include the =
libxml libraries=20
(libxml2.dll and libxslt.dll) in the Windows Setup package=20
?</FONT><BR><BR>Thanks,<BR><BR>Gert<BR></DIV></BODY></HTML>
------=_NextPart_000_005C_01C2E356.F0BD5DF0--