 - Visual J# (sometimes known as just J#) is a set of programmming tools that allow developers to use the Java programming language to write applications that will run on Microsoft's .NET runtime platform.
While Microsoft does not support the Java virtual machine as part of .NET, Visual J# allows a programmer familiar with or who prefers Java's concepts and language syntax to write and compile a program that will run successfully on the .NET Framework Common Language Runtime platform. The source statements are compiled into Microsoft Intermediate Language (MSIL), which is the equivalent of Java bytecode. A program already compiled into Java bytecode can be converted into MSIL.
With Visual J#, Microsoft includes their own class libraries that are the equivalent of the Java Development Kit level 1.1.4 class libraries. Visual J# supports the functionality of Visual J++ and Microsoft extensions. For Visual J++ users, Microsoft says that Visual J# presents a familiar interface and both development systems and project files can be used on the same machine.
A source file written in Visual J# will by default have the file name suffix .jsl.
 |
Learn more about Microsoft .NET Web services |
| SOA policy: Enterprise logic vs. application logic: The future of SOA policy is moving towards an approach that may put business people in the driver's seat, predicts Miko Matsumura, vice president and deputy CTO for Software AG. |
| Java versus Microsoft for SOA: Is Java gaining the edge over Microsoft .NET in SOA development as a recent survey indicates? Two industry analysts offer contrasting views. |
| Deutsche Post delivers .NET in Java CRM thanks to SOA: An integration expert at Deutsche Post finds a way to bring .NET applications into a CRM system that is part of a Java-based service-oriented architecture (SOA). |
| SOA policy beyond Java and .NET: SOA policy needs to move beyond the Java and .NET platforms that may be used to build services, argues Miko Matsumura, vice president and deputy CTO for Software AG. |
| Using ADO.NET and SDO for SOA data continuity: Both ADO.NET and SDO use XML to enable data transfer between disjointed components inside an SOA, enabling developers to create all kinds of new Web services mashups. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| Decision time: .NET or J2EE?: How do .NET and J2EE stack up against one another? That depends on who you ask. We've compiled resources from both sides of the fence to help you decide for yourself. |
| .NET Crash Course: Our .NET Learning Guide along with other resources will bring you up to speed on .NET. You'll find .NET articles, tutorials, tips, tools, white papers, expert advice and more. |
| .NET Learning Guide: This guide introduces you to .NET, explains best practices and pitfalls to avoid and provides troubleshooting help and advice. |
| Crash Course: J2EE and .NET interoperability: Get some tips for .NET and J2EE interoperability with our webcast, free chapter and other resources. Then, take a quiz to win a copy of .NET and J2EE Interoperability. |
| LAST UPDATED: |
04 Aug 2002
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
