# Friday, May 7, 2004
« Mono Beta 1 | Main | Generics Again »
Assembly Names

To clean up the assembly names, I propose to change to the following names for the next snapshot:

Current Name New Name
awt.dll IKVM.AWT.WinForms.dll
classpath.dll IKVM.GNU.Classpath.dll
ik.vm.jni.dll IKVM.JNI.CLR-Win32.dll
ik.vm.net.dll IKVM.Runtime.dll
ikvm.exe ikvm.exe
ikvmc.exe ikvmc.exe
Mono.IKVM.JNI.dll IKVM.JNI.Mono.dll
netexp.exe ikvmstub.exe
OpenSystem.Java.dll (will be removed)

I'm removing OpenSystem.Java.dll for the time being, because interop with dotGNU hasn't really happened so far and at this point it's just pre-mature design for reuse. Hopefully, in the future when they continue their work on Java support we can work together to make the two systems interoperable.

Any comments on the assembly names?

[Update: Stuart makes a good point in the comments. I've changed the suggested new name of netexp to ikvmstub.exe]

Friday, May 7, 2004 3:52:52 PM (W. Europe Daylight Time, UTC+02:00)  #    Comments [1] Tracked by:
"bad effect of diet pills" (bad effect of diet pills) [Trackback]
"poker online no download" (poker online no download) [Trackback]

Friday, May 7, 2004 5:13:55 PM (W. Europe Daylight Time, UTC+02:00)
I like them, but have you considered putting "ikvm" into the name of netexp somewhere, eg "ikvmexp" or "ikvmstub"? The name "netexp" is very generic - even if you know what the two halves stand for ("dot net exporter", more or less, I guess), it still doesn't tell you anything about the actual purpose of the program. Export from dot net to what?

Also, "dot net" is an MS-specific name.

And all your other names have ikvm in them.

I kind of like "ikvmstub" because that's what it really does - produces stub jar files that can be compiled against. In that regard, it performs a similar function to an IDL compiler, except that the IDL is a CLI API exposed by reflection.
Comments are closed.