The information presented below has been categorized into discreet content "focuses": You can jump to any specific section by selecting from the following list:

Overall, .NET is a set of products, SDK's, and development tools that enables a broad range of applications to be created (e.g. Web Services, Web Sites, Desktop Applications, Business Components, etc.). However at its core, .NET is an architecture for the creation, deployment, and management of XML Web Services.

The J2EE (which stands for Java 2 platform, Enterprise Edition) platform consists of a set of services, APIs, and protocols that provide the functionality for developing multi-tiered, Web-based applications. J2EE also supports XML Web Services, however for the most part their implementation has been left to the specific J2EE Application Server providers (e.g. IBM, Web Logic, etc.). A future release of J2EE will consolidate this XML Web Services fragmentation into one standard.

Top
2). Which technology (.NET or J2EE) should I use?

As with most things in life, the answer is "it depends". For the most part, we do not feel that this is an either/or answer for the majority of businesses. Many mid-to-large sized companies with implement and support both technologies. However some guidelines that can be used in selecting a either technology for a candidate project are...

• Will the application in question need to access a variety of different backend data sources? If so, then .NET may be the correct choice. ADO.NET can access virtually any relational database, XML/Text file store, and or legacy system (via messaging) with one development model. You can achieve the same success with J2EE, however you will have different (if not custom) models for database, XML/File, and host based access.
• What type of infrastructure staff do you have? Those companies that have infrastructure groups comfortable with UNIX/Linux servers should look at J2EE. Thos companies that have Windows NT/2000 server should look at .NET.
• What type of Email services do you use? If you run Microsoft Exchange, .NET is for you. If you run something else (e.g. Lotus Notes, etc.) then it is probably a toss up between .NET and J2EE. .NET supports a unified interface in to electronic mail systems (e.g. SMTP, CDO, LDAP, etc. is all handled the same way). J2EE provides separate interfaces for each mail platform.
• What type of application developers do you have? J2EE only supports the Java language. .NET supports a variety of languages (e.g. Visual Basic, C++/C#, Java, Cobol, Fortran, etc.). Retraining developers can be costly and time consuming.

No. .NET the next evolutionary step for Microsoft. With the advent of Web Services, the fundamental way organizations integrate and build both internal and external applications will change. .NET is Microsoft's framework to enable and build these new types of solutions.

Top
2). Isn't .NET a closed platform controlled by one vendor?

Essentially yes. Most of the .NET Framework is defined by and controlled by Microsoft (the exceptions being that C# and the Common Language Specification have been submitted to the ECMA). However, .NET natively supports XML, SOAP, WSDL, UDDI, IPSec, RSA, LDAP, HTTP, SMTP, and other standards as primary interfaces and protocols. Proprietary protocols (like COM) still exist but are only available for legacy support and to satisfy special needs.

J2EE is essentially a closed platform as well. Contrary to popular belief, J2EE is tightly controlled by Sun (it is portions of the Java "Standard Edition" that has been opened up). Those companies building products and services around J2EE have to agree to and conform to the Sun licensing restrictions.

Yes and No. Currently .NET on runs on the Microsoft Windows and Windows XP platforms. Microsoft is current working with third-party vendors who are converting the .NET framework to other operating systems (the only thing machine/OS specific about the .NET Framework is the Common Language Runtime). So hopefully soon you will be able to run .NET applications on Linux and Unix.
Go to the top of the page