Hi Armin,
well, it would be much
better to eliminate any references and static/dynamic
imports to that library since you will not know (unless
you explicitly do not allow to run on a different OS
than XP) where someone will start your application. If
you are ok with the fact and you are ready to deal with a
runtime exception, then its ok,..but in reality who will?
I personally recommend not to use the msjava.dll. Peter
should have a look at what his application is linking to
from the msjava.dll by using dependency walker and should
try to find a replacement either in windows api or in another
library that is available on any windows platform. If he hardly
depends on java functionality, then he could scan the system
(filesystem or registry but registry is recommended and first hit)
for any installed java runtimes (mostly sun is available) and check
the java version available, prompting user on fail for missing java
runtime or version.
This whitepaper is higly recommended for java to .net "defectors",... *g*
[Moving Java Applications to .NET]
http://msdn.microsoft.com/en-us/library/ms973842.aspx
There is also the JNI (Java Native Interface)
http://en.wikipedia.org/wiki/Java_Native_Interface
He should have a look at this, too:
https://jna.dev.java.net/
msjava.dll is dead,..we have to deal with that!