Java User Migration Path to Microsoft .NET (JUMP to .NET) is a set of independently developed technologies and service offerings that enable programmers to preserve, enhance, and migrate Java-language projects onto the Microsoft .NET platform.
- Posted by: quin ying
- Posted on: January 26 2001 13:14 EST
- Microsoft announces Java Migration Path for .NET by sharat babu on January 26 2001 19:33 EST
- Microsoft announces Java Migration Path for .NET by Chad Bradley on January 30 2001 15:34 EST
- Microsoft announces Java Migration Path for .NET by Senthil Radhakriahnan on February 05 2001 04:28 EST
- Microsoft announces Java Migration Path for .NET by Usha Iengar on February 05 2001 20:27 EST
- Microsoft announces Java Migration Path for .NET by jakob raderius on February 06 2001 07:47 EST
This is a really good motivation by MS.
The title should be j++ not java.j++ isn't java at least not if you're using all the com/dcom or windows foundation classes. Sorry not impressed.
I think MS is talking about moving code from Java to C#, not
You mean that of the few people out there that actually ever used J++, some still have J++ apps deployed?
Surprising Microsoft is actually supporting one of their dead technologies...
Hopefully J++ users learned their lesson the first time.
Read the article. It's a bunch of crap. M$ is talking about tools to migrate j++ code and "teach" java coders how to use .net all in one article hoping to confuse you.
Sad in certain ways. The best Java IDE is now gone forever.
What is the best java IDE? InterDev? Please!!
This article is CRAP all the way!
How can Microsoft even talk about XML-based Web Services when they once again have proved that they don´t understand the concept of open standards and ONCE AGAIN have made their own non-standard-compliant hybrid called "Microsoft XML".
As for the rest, why would someone ever wan´t to convert portable Java code into Microsoft platform specific...things like C#.
This thread : https://theserverside.com/discussion/thread.jsp?thread_id=4306 might also be of interest in the - J2EE vs M$ .NET debate...