Guenther Roith wrote:

I think we should do the following:
* write a mscorwks.dll & installation that puts it in the correct
directory (and possibly registry). This mscorwks.dll should locate the
mono environment and use it to execute the application
* write a mscoree.dll & installation (in one of the system directories)
that locates the mono base directory and hands execution to mscorwks.dll

This could easily be included in the windows setup.

- Look for Registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\InstallRoot"
This contains something like "c:\winnt\Microsoft.NET\Framework".

- Create a new directory "mono" in there.

I don't think that will work, because it must be a 'version' directory (vx.x.x.x format)
(that's also why we need a version number that won't conflict with a microsoft number)

- Copy mscorwks.dll there. NOTE: On servers mscorsrv.dll is called!!!! (We
must do both.)

Yep, but for now we can have one just call the other (or duplicate dlls), they contain the same functionality, just optimized for single/multiple CPUs as far as I could find out.

I can add this to the lcc program, that already does the windows setup.

That would be nice indeed.
---
Jeroen


_______________________________________________
Mono-list maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to