Lambda the Ultimate

inactiveTopic Microsoft Visual J# .NET Beta 2
started 3/20/2002; 2:28:28 AM - last post 3/20/2002; 8:45:48 AM
Dan Shappir - Microsoft Visual J# .NET Beta 2  blueArrow
3/20/2002; 2:28:28 AM (reads: 2029, responses: 5)
Microsoft Visual J# .NET Beta 2
The tool integrates the Java-language syntax into the Microsoft Visual Studio® .NET IDE, and supports the functionality found in Visual J++® 6.0, including Microsoft extensions such as JavaCOM and JDirect.

Also note that:

Microsoft Visual J# .NET is not a tool for developing applications intended to run on a Java virtual machine. Applications and services built with Visual J# .NET will run only in the .NET Framework; they will not run on any Java virtual machine.

And obviously:

Visual J# .NET has been independently developed by Microsoft. It is not endorsed or approved by Sun Microsystems, Inc.

I truly wonder if anyone will use this, and if so why.

Posted to cross-language-runtimes by Dan Shappir on 3/20/02; 2:29:36 AM

mattias waldau - Re: Microsoft Visual J# .NET Beta 2  blueArrow
3/20/2002; 2:41:13 AM (reads: 899, responses: 0)
If you had been using Microsofts developments tools, you wouldn't ask "I truly wonder if anyone will use this, and if so why."

Java-developing tools are pathetic compared to MS. (IntelliJ IDEA is the only exception).


Dan Shappir - Re: Microsoft Visual J# .NET Beta 2  blueArrow
3/20/2002; 5:18:34 AM (reads: 871, responses: 0)

I use MS development tools regularly (in fact I have both VS6 and VS.NET installed on my working machine), and indeed MS fine dev-envs makes. I also have both VisualCafe and JBuilder installed, and I do prefer VS to both, though this preference may also be the result of familiarity (if you have them, note the similarity between JBuilder and VS.NET. Must be the result of MS stealing all those Borland developers. I am not familiar with IntelliJ.)

Despite my preference, I do not consider using VS.NET and J# to develop Java applications. The only reason I develop applications in Java is to have them run on the JVM. For .NET I only use C# (and sometimes VB.NET and JScript.NET for laughs.) The only reason I see for using J# is if you were gullible enough to make a large investment in VJ++ and are now stuck with the code. In that context J# may be a lifesaver (though a bit late IMO).

Using J# as a means for leveraging Java knowledge for .NET is wrong, a mental dead end. Better to bite the built and go with C# (which is close enough anyway).

BTW, I wonder if J# has inner classes.

nickmain - Re: Microsoft Visual J# .NET Beta 2  blueArrow
3/20/2002; 7:28:16 AM (reads: 872, responses: 1)
I did consider this as a quick way to make an existing Java library available as a dotNET package. The reason I backed off is that J# has a large runtime overhead beyond that of the dotNET Framework (essentially CLR versions of all the JDK 1.1 framework classes) - the extra download wasn't acceptable.

Instead, I'm looking to templatize the library - using JSP. The hope is that I can generate either C# or Java source from the same set of templates.

Has anyone else tried this sort of thing ?

Dan Shappir - Re: Microsoft Visual J# .NET Beta 2  blueArrow
3/20/2002; 7:50:19 AM (reads: 919, responses: 0)
This sounds sort of similar to (the now defunct) gen<x>.

nickmain - Re: Microsoft Visual J# .NET Beta 2  blueArrow
3/20/2002; 8:45:48 AM (reads: 852, responses: 0)
Yes - I looked at Gen<X> when it first came out. JSP has custom tags (does ASP ? ..never used it.) which seem like a nice way to separate the template content from the control logic and to abstract away the differences between C# and Java.

Thus (a JSP fragment with custom tags):

<x:class public='true' name='Foo'>
        for( int i = 0; i < 10; i++ )
            <x:println/>( "Hello World " + i );

Could spit back either Java or C# depending on a query-string or form-post parameter.