« Good Ant Tip | Main | AppFuse 1.3 vs. 1.4 »
20040217 Tuesday February 17, 2004

Write your Java apps in Visual Studio.NET? Apparently Visual MainWin allows you to write your webapps in C# and .NET and then deploy them to a J2EE server.

Visual MainWin for J2EE enables these organizations to deploy .NET and J2EE applications on a single J2EE infrastructure, eliminating the need to maintain two separate application servers or implement complex interoperability solutions between the .NET and J2EE platforms.

This product certainly won't do anything for me. I've heard that Visual Studio is a great IDE, but if I can't write Java in it - what's the point?

how it works

Then again, I'm biased. I have a friend who is a long-time Java developer. Lately, he's been developing in C# because that was the only gig he could get (in Nevada). He says that C# is a piece of sh*t compared to Java.

Update: My friend contacted me to set the record straight. To quote him, "C# is OK, its the .NET framework that sucks ass. The C# syntax is a total ripoff of Java anyways." Posted in Java at Feb 17 2004, 12:20:00 PM MST 21 Comments

Comments:

Correction you can write Java in Visual Studio, they have a module called Visual J#.

Posted by andres on February 17, 2004 at 12:33 PM MST #

Thanks for the clarification Andres. Now the real question is - <strong>How much does it cost?</strong>

Posted by Matt Raible on February 17, 2004 at 12:37 PM MST #

J# is not Java

Posted by Unknown on February 17, 2004 at 01:58 PM MST #

I don't know why people always thinks Visual Studio is great. That opinion always stems from two categories of people: those who have never tried it, and those who have never tried anything else. I use it regularly (have to), and compared to the IDEs on the Java side it really is crap!

Posted by Madsie on February 17, 2004 at 03:55 PM MST #

Good to know Madsie - your insight is appreciated. I definitely love Eclipse and IDEA - both are high quality products.

Posted by Matt Raible on February 17, 2004 at 09:07 PM MST #

Well coming from the Java world, and developing in C# myself, I have to say that the "C# is crap" comment really does not do C# justice. C# is so close to Java in syntax and sematics that it is unfortunate that Java developers would not give it is closer look. From my own experience, moving from Java to C# and back is almost seamless. Getting to know the .NET framework is where the hard part is, but in this day and age code introspection helps ease that pain. For example, at my job, I converted one of my Java web services (2300 LOC) to C# in a matter of 3 days. This included: 1. Manual Java to C# syntax conversion 1. Converting logging code from log4j to log4net. 2. Converting XML/DOM/XPath code from dom4j to System.XML namespace. 3. Converting database access code from JDBC to ADO.NET (Firebird .NET provider). The fact that this conversion was so smooth says alot for the design of the C# language and the .NET Framework itself. As an everyday Eclipse and WSDD user, I actually like VS.NET alot, especially for developing WinForms and Compact Framework.

Posted by dsuspense on February 18, 2004 at 12:23 AM MST #

As far as I understand they do not have J# module (maybe just yet :-). The point is as follows : you can't write Java language in VisuialStudio but you do have an access to all Java SDK libraries and functionality from this tool (and you are programming in C#). From the developer's point of view in addition of standard .NET namespaces you also have additional java.* (or sun.* or whatever you have in classpath) namespace(s).

dsuspense You're totally right! I did it a lot of times - just copy/paste from Java to C# and vise versa, some syntax corrections - and the code is working (howewer it relates to the code that is not using .NET framework classes.)
Any additional comment are welcome.

Posted by kir on February 18, 2004 at 02:18 AM MST #

Comments on my blog at http://www.jroller.com/page/arjunram/20040218#re_write_your_java_apps btw, have u disabled trackbacks?

Posted by Arjun Ram on February 18, 2004 at 06:37 AM MST #

I do have Trackbacks disabled because my <em>Google number</em> is above 32,000. I think I was getting a lot of my OutOfMemory errors from Roller crawling so many referring sites. Who knows - I guess I could try turning it back on again. Maybe next week...

Posted by Matt Raible on February 18, 2004 at 08:06 AM MST #

I think you are confusing Trackback and Linkback. <p /> Linkback is the facility that follows referer links, parses pages, and figures out if somebody is linking to you in a weblog post. That is expensive and we turn it off on JRoller too. <p /> Trackback, on the other hand, is a really simple web service. When Arjun, or some other blogger writes about you he has the option of sending you a trackback ping - very inexpensive for both your server and Arjun's server. I don't think you can turn off trackback in Roller. Maybe trackback is broken on your site or in Roller 0.9.9-dev?

Posted by Dave Johnson on February 18, 2004 at 12:42 PM MST #

Dave - you are correct, I have Linkback turned off. After looking at my config settings - it doesn't look like I can turn off Trackback. It definitely could be broken.

Posted by Matt Raible on February 18, 2004 at 01:02 PM MST #

Why would anyone in their right mind write Java (J#) code for .Net anyway? I'll stick with Eclipse and JBoss, thank yoU!

Posted by jeff on September 25, 2004 at 07:35 PM MDT #

C# is a solid copy of JAVA with a few more disadvantages and .NET is a total windows job, forcing coders to store information inside of a form and then the forced style of coding (i.e. needing a "break;" command at the end of a switch statement POINTLESS!!!) not to mention C#'s incompatability with non-windows encoding methods (like .mid for sound, .avi for video and .png for images, etc) also the lack of online support for C# makes it harder to use and the limited and jumbled library methods means that already the current visual studio environment does not support older program's limiting the shelf life of anything written and meaning that every large C# implementation will eventually upgrading to some degree. just to get a nice windows form (comparable to any JAVA flow layout visual plugin) isn't wort the downside or the frustration suffored by programmers (and why would anyone want to bother with enum, echar, etc when its all been taken care of since C++ ???)

Posted by Rafferty on December 19, 2007 at 05:53 PM MST #

I can see this is an old thread but I stumbled on it so just wanted to make sure folks who stumble on it like i did get a bit of fact in regards to Rafferty's comments. 1. C# nor .Net require storing information in a form and the practice is actually discouraged. Inexperienced programmers or those inexperienced with Visual Studio tend to do this but is not an acceptable practice. 2. "break;" is required in switch statements in C#, Java, C++, ... to make the flow work correctly. You can write a switch without the "break" but you will likely experience bugs that are difficult to track down later. 3. C# is fully compatible with each of the formats mentioned and is all about online communication, thus the name .NET 4. Each version of the .NET framework has been mostly backward compatible with previous versions except where functionality was replaced due to security concerns. 5. WinForms layout engine could be better but it really is just a different way of dealing with things than Java. I have used both and have become comfortable with both but saying C# or .NET suck because it isn't like what you are comfortable with is not a valid assessment. Programming languages and IDEs are tools in your toolbox. Use the correct tool for the correct situation and you will be happier. If you don't like a tool, that doesn't mean it isn't a good tool just that you don't like it. If you are developing for windows, Visual Studio can provide a lot of advantages, if you are writing exclusively in Java, maybe JBuilder or Eclipse is better. But that doesnt mean everything else sucks.

Posted by Dave Buhl on October 23, 2008 at 04:31 PM MDT #

I can see this is an old thread but I stumbled on it so just wanted to make sure folks who stumble on it like i did get a bit of fact in regards to Rafferty's comments. 1. C# nor .Net require storing information in a form and the practice is actually discouraged. Inexperienced programmers or those inexperienced with Visual Studio tend to do this but is not an acceptable practice. 2. "break;" is required in switch statements in C#, Java, C++, ... to make the flow work correctly. You can write a switch without the "break" but you will likely experience bugs that are difficult to track down later. 3. C# is fully compatible with each of the formats mentioned and is all about online communication, thus the name .NET 4. Each version of the .NET framework has been mostly backward compatible with previous versions except where functionality was replaced due to security concerns. 5. WinForms layout engine could be better but it really is just a different way of dealing with things than Java. I have used both and have become comfortable with both but saying C# or .NET suck because it isn't like what you are comfortable with is not a valid assessment. Programming languages and IDEs are tools in your toolbox. Use the correct tool for the correct situation and you will be happier. If you don't like a tool, that doesn't mean it isn't a good tool just that you don't like it. If you are developing for windows, Visual Studio can provide a lot of advantages, if you are writing exclusively in Java, maybe JBuilder or Eclipse is better. But that doesnt mean everything else sucks.

Posted by Dave Buhl on October 23, 2008 at 04:32 PM MDT #

I can see this is an old thread but I stumbled on it so just wanted to make sure folks who stumble on it like i did get a bit of fact in regards to Rafferty's comments. 1. C# nor .Net require storing information in a form and the practice is actually discouraged. Inexperienced programmers or those inexperienced with Visual Studio tend to do this but is not an acceptable practice. 2. "break;" is required in switch statements in C#, Java, C++, ... to make the flow work correctly. You can write a switch without the "break" but you will likely experience bugs that are difficult to track down later. 3. C# is fully compatible with each of the formats mentioned and is all about online communication, thus the name .NET 4. Each version of the .NET framework has been mostly backward compatible with previous versions except where functionality was replaced due to security concerns. 5. WinForms layout engine could be better but it really is just a different way of dealing with things than Java. I have used both and have become comfortable with both but saying C# or .NET suck because it isn't like what you are comfortable with is not a valid assessment. Programming languages and IDEs are tools in your toolbox. Use the correct tool for the correct situation and you will be happier. If you don't like a tool, that doesn't mean it isn't a good tool just that you don't like it. If you are developing for windows, Visual Studio can provide a lot of advantages, if you are writing exclusively in Java, maybe JBuilder or Eclipse is better. But that doesnt mean everything else sucks.

Posted by Dave Buhl on October 23, 2008 at 04:32 PM MDT #

I can see this is an old thread but I stumbled on it so just wanted to make sure folks who stumble on it like i did get a bit of fact in regards to Rafferty's comments. 1. C# nor .Net require storing information in a form and the practice is actually discouraged. Inexperienced programmers or those inexperienced with Visual Studio tend to do this but is not an acceptable practice. 2. "break;" is required in switch statements in C#, Java, C++, ... to make the flow work correctly. You can write a switch without the "break" but you will likely experience bugs that are difficult to track down later. 3. C# is fully compatible with each of the formats mentioned and is all about online communication, thus the name .NET 4. Each version of the .NET framework has been mostly backward compatible with previous versions except where functionality was replaced due to security concerns. 5. WinForms layout engine could be better but it really is just a different way of dealing with things than Java. I have used both and have become comfortable with both but saying C# or .NET suck because it isn't like what you are comfortable with is not a valid assessment. Programming languages and IDEs are tools in your toolbox. Use the correct tool for the correct situation and you will be happier. If you don't like a tool, that doesn't mean it isn't a good tool just that you don't like it. If you are developing for windows, Visual Studio can provide a lot of advantages, if you are writing exclusively in Java, maybe JBuilder or Eclipse is better. But that doesnt mean everything else sucks.

Posted by Dave Buhl on October 23, 2008 at 04:32 PM MDT #

Hi Do you know any pluging for vs.net that could programming java in vs.net IDE ? if yes please email me .

Posted by me on November 13, 2008 at 09:56 AM MST #

Hi Do you know any pluging for vs.net that could programming java in vs.net IDE ? if yes please email me .

Posted by me on November 13, 2008 at 09:58 AM MST #

SDDSAFSDFS

Posted by 85.250.226.239 on December 23, 2008 at 01:09 AM MST #

llllllllllllllllllll

Posted by 212.138.69.18 on March 21, 2009 at 04:20 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed