Definition

Visual J#

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.

This was last updated in September 2005
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: