I did a Webcast yesterday that’s online now. You can view the archive of that here:
Several people have asked whether or not it’s still important to migrate away from the MSJVM in light of the April 2nd announcement. While the deadline has been extended for us to support the MSJVM, organizations still need to move away from the MSJVM for several reasons:
1) Microsoft can only fix critical and security-related bugs with the MSJVM. This means that any bugs not falling into those categories can not be fixed as per Microsoft’s agreement with Sun.
2) Microsoft cannot enhance the MSJVM. Unless your application or applet is scheduled to be retired, this obviously can limit the amount of innovation you can do with your applet/lication.
3) Microsoft cannot fix any bugs, even security bugs, after December 31, 2007. This means that if you have the MSJVM installed on any machines, you do run a potential security risk.
Migrating to .NET is just one way of getting off of the MSJVM. My webcast focuses on migration to .NET.
MSDN Webcast: Microsoft Java Virtual Machine Transition
The recent announcement between Microsoft and Sun Microsystems has extended the end-of-life deadline for the MS JVM to December 31, 2007. But Microsoft can still only support critical security bugs during this time, and Microsoft can no longer enhance the functionality of the MS JVM. If you want to learn how to migrate your MS JVM-based applications to the .NET Framework and take advantage of a modern, fully-supported developer platform, then you should view this previously-recorded Webcast. This Webcast covers key migration scenarios using J# and the Java Language Conversion Assistant. Click here to view the webcast archive.