Visual J++ (pronounced "Jay Plus Plus") is Microsoft's discontinued implementation of Java. Syntax, keywords, and grammatical conventions were the same as Java's. It was introduced in 1996 and discontinued in January 2004, replaced to a certain extent by J# and C#.
While J++ conformed to the Java language specification, Microsoft did not implement certain features of the official Sun Java implementation in its Visual J++ product line. Remote Method Invocation (Java RMI) and Java Native Interface (JNI) are such examples.
In addition, J++ implemented other extensions that were not part of Sun's Java implementation. The inclusion of callbacks and delegates for event handling further contributed to defining J++ as a completely different language merely based on an already existing design concept.
Furthermore, J++ applications did not conform to the same standardized method of accessing the underlying operating system functions as any other Java application under Sun's Java SDK. In Microsoft's implementation, an underlying framework called J/Direct provided a base mechanism that allowed J++ applications to completely circumvent Java's class libraries and API in accessing the underlying operating system. Due to this short-cut around the original Java framework, J++ applications were more efficient in taking advantage of Win32 API functions than Java applications.
J++ applications using these features could not be run on Sun's Java SDK, but the Kaffe project developed extensions which made it possible to run J++ applications with these features on their open sourced JVM. However, these extensions (implemented by TransVirtual under Microsoft funding) were not widely used, and J++ applications still needed to be compiled on Visual J++ before being able to be run by Kaffe.
The Windows Foundation Classes (WFC) encapsulated the Microsoft Win32 platform API and DHTML object models into a unified class library. WFC was primarily designed for creating graphical user interfaces for Java applications on Windows.
Sun Microsystems had originally licensed Java to Microsoft but later initiated litigation against Microsoft for trademark violation. Sun's trademark license for usage of the Java brand insists that all implementations be "compatible".
The failure of the MSJVM to pass Sun's compliance tests was a large factor in the initial lawsuit. In 2004, this and all other outstanding Sun–Microsoft lawsuits were settled as part of a wide-ranging agreement between Sun and Microsoft. As provided in the settlement, Microsoft could not incorporate into J++ features that Sun introduced into Java in versions beyond the one J++ had (at that date) been mirrored from; it would be frozen at the feature set of Java version 1.1.4. This effectively killed J++, and ended further updates. Microsoft was also forced to agree to cease distribution of the MSJVM; it is no longer available for download.
The terms of the settlement did, however, permit Microsoft to provide security support, allowing further updates to the MSJVM to fix security holes and any other problems relating to security threats. Microsoft ceased such support for the MSJVM on December 31, 2007.
Visual J# (pronounced "Jay Sharp") is a Microsoft language whose syntax is close to Java, part of the .NET Framework. Visual J# is part of the Microsoft Visual Studio .NET product suite and is designed to help developers and programmers migrate from J++ (or Java) to the .NET Framework.
Microsoft later developed the C# ("C Sharp") language as the primary language for the .NET platform, which was in many ways influenced by Java; subsequently the .NET Framework shares many ideas in common with Java. Much like Java, C# is compiled to a type of bytecode (called CIL), and runs on top of a virtual machine called the Common Language Runtime in .NET. Visual Studio 2005 was the last release to include J#.
A September 1997 E-mail message, sent by a Microsoft official identified as P. Sridharan, is quoted as saying: "Let's move on and steal the Java language. That said, have we ever taken a look at how long it would take Microsoft to build a cross-platform Java that did work? Naturally, we would never do it, but it would give us some idea of how much time we have to work with in killing Sun's Java."
We should just quietly grow j++ share and assume that people will take more advantage of our classes without ever realizing they are building win32-only java apps.
Edited: 2021-06-18 15:18:13