Microsoft .NET
From Wikipedia, the free encyclopedia.
The .NET (note capitalization) initiative is a Microsoft project to create a new software development platform focused on network transparency, platform independence, and rapid application development.
| Table of contents |
|
2 The Enterprise Infrastructure 3 Supporting Products 4 .NET Languages 5 .NET vs. J2EE 6 .NET vs. COM 7 Standardization 8 Alternative Implementations 9 External links |
The Strategy
First, .NET is a strategic initiative. .NET includes many technologies which are designed with the Internet in mind.
The Enterprise Infrastructure
Second, .NET is a software platform, which was released in 2002. It presents a platform-independent target for software development, with many built-in features including Internet integration and features intended to enhance security. It relies fully on the software componentry and component-oriented programming paradigms. In this respect it largely replaces the former component object model (COM).
- The Common Language Infrastructure (CLI) is a virtual machine and a standard class library (the Common Language Runtime which is designed to be independent of both programming languages and operating systems). The virtual machine executes the Microsoft Intermediate Language (MSIL) assembly.
- Access to components written in other languages and the underlying Microsoft Windows platform
- Web services using the SOAP
Supporting Products
Third, .NET is a collection of development environments and software packages that are new versions of existing Microsoft products geared toward the .NET platform, including a more advanced Visual Studio.
.NET Languages
The CLI is designed to provide support for any object-oriented programming language, sharing a common object model and a large common class library.
Microsoft and other vendors provide .NET versions of many languages, including:
- C# programming language, an object-oriented language similar to Sun's Java
- Visual Basic .NET, an improved, object-oriented, multi-threaded version of the classic Visual Basic programming language
- ASP.NET, an improved, object-oriented version of the classic Active Server Pages (ASP) web programming language
- Managed C++, a variant of the C++ programming language for the .NET platform
- Jscript .NET, a compiled version of Microsoft's JScript, quite similar to ECMAScript
- Lexico, a didactic in Spanish objects oriented language.
- Delphi 8 which is also called Delphi for .NET is a full .NET compatible language. Delphi 8 is available since Dec 2003 and running quite stable.
- COBOL
- Perl
- Python
- Mercury
- Objective Pascal
- F sharp programming language
- Lisp
- Forth
- J#, a Java and J++ (the Microsoft variant of Java) .NET transitional language
- Nemerle functional/imperative hybrid language
- many of these compilers are free (the vendors sell IDEss).
- most languages have significant adjustments to fit into the .NET Framework. The vendors have often used this as an excuse to vary other features of the languages at the same time.
.NET vs. J2EE
The CLI, the MSIL and C# have similarities to Sun Microsystems' Java Virtual Machine and Sun's Java, hence they are fierce competitors. Both use their own intermediate bytecode. .NET is currently only fully available on Windows platforms, whereas Java is available on many platforms. Sun's product, J2EE, provides equivalent functionality to other Microsoft technologies such as COM+ (previously MTS) and MSMQ which are tightly integrated into the Windows operating system. .NET components make full use of these existing technologies in an abstracted manner.
.NET vs. COM
The previous software component technology endorsed by Microsoft for large-scale software systems was the Component object model or COM, using COM+ or MTS enhancements for distributed transactional components. While .NET may wrap COM-objects and vice versa, it has been clearly stated by Microsoft that .NET will eventually replace COM as a software component architecture. New applications addressing the Win32 platform should not use COM, but .NET, with use of existing services via abstracted interfaces (e.g. transactional .Net components currently use COM+).
Standardization
Microsoft has submitted a part of the specifications of .NET to ECMA and ISO for standardization. This is a calculated risk, but it may encourage standards-compliant implementations, to provide an ongoing bridge for non-Windows software to be converted to Microsoft .NET.
Alternative Implementations
While the Microsoft .NET Framework is the flagship implementation of .NET technologies, there exist other implementations.
Mono is an open source implementation of the .NET runtime and development libraries. It is quickly maturing, including support for ASP.NET and evolving support for Windows Forms libraries. Mono also includes the development of new libraries and technologies, which include:
- Gtk#: A .NET wrapper for the Gtk+ GUI toolkit.
- XSP: A web server written in C# with support for hosting ASP.NET applications.
- MonoDevelop: A port of SharpDevelop, a GPLed IDE for .NET, to Gtk# and Mono.
- Novell.Directory.Ldap class libraries: A free implementation of LDAP support for .NET.
Microsoft Rotor, or the Shared Source Common Language Infrastructure is an open source implementation of the .NET Framework by Microsoft. It runs on Microsoft Windows XP, FreeBSD, and Mac OS X 10.2.
External links
- Microsoft's official .NET Resource
- TheServerSide.Net
- GotDotNet
- Ximian's Mono Project, an Open source implementation of the .NET Framework
- Guidelines to referencing the Microsoft® .NET brand
In Internet nomenclature, .net is a Top-level domain, or TLD, as is .com.