 |
NET2Java
translates applications written either in Visual Basic or in C#, 2003
or 2005 editions.
|
 |
 |
Ya,
that much source code. |
 |
 |
NET2Java
creates readable Java source
code; e.g. it preserves class names, method names and code comments. |
 |
 |
Because
your applications don't stand still, they will evolve. |
 |
 |
NET2Java uses the NET2Java Library to translate
.NET API calls into Java
Platform API calls. |
 |
 |
Because
.NET programs usually make lots of .NET platform API calls. |
 |
 |
NET2Java doesn't sweat it when it encounters an
unknown API call: it flags it for later and keeps on translating. |
 |
 |
Because
many of your .NET applications use custom components that I've never
heard of. |
 |
 |
NET2Java
includes the NET2Java NetBeans Plugin to let you 'import' a .NET
project into a NetBeans project. |
 |
 |
Because
I *heart* NetBeans. |
 |
 |
NET2Java
includes some homemade .NET samples for you to try translating. |
 |
 |
Because
the best way to understand it is to try it. |
 |
 |
I've
filled the NET2Java Library with enough translations to translate the
samples, and a little more. |
 |
 |
Because
I haven't had time to fill up the NET2Java Library myself. |
 |
 |
The NET2Java Library Editor makes it super
easy to add translations to the NET2Java Library. |
 |
 |
Because
I want to make it easy for us to team together to fill up the NET2Java
Library with a translation for every .NET API call. |
 |
 |
I've
had a lot of fun creating NET2Java. |
 |
 |
And
I think you might have fun too. |
 |
 |
If
you're interested in NET2Java, come help !
|
 |
 |
Because
together we can translate all the .NET applications. |
 |