Microsoft .NET has been the brand name for Microsoft's suite of development tools for several years now. Microsoft previously packaged all of their tools under the product name "Microsoft Visual Studio," which had 6 versions until the name was dropped in favor of the more ambitious Microsoft .NET.

The creation of the Microsoft .NET framework was more than just a rebranding effort. The company was facing a serious challenges to its market share from Sun, makers of Java, and PHP (PHP Hypertext Processor), a scripting language. The answer to this challenge was to create C# (pronounced C Sharp), which could reasonably compete with Java on ease-of-use and functionality. This meant a revamp of Visual Basic and C++ (creating Visual Basic.NET and C++.NET respectively.)

.NET software has been a credit to Microsoft. Almost instantly, it reaffirmed Microsoft's position as the dominant provider of desktop and web development tools. With the release of Microsoft .NET Framework 2.0, 3.0, and 3.5 Microsoft .NET has become the standard for enterprise eCommerce development for many IT shops. These companies are engaging in Microsoft .NET eCommerce development for a number of reasons:

1. Microsoft .NET was designed with web development in mind (hence the name .NET)
2. Technologies like Silverlight (the Microsoft .NET Flash competitor) make .NET eCommerce development functional and beautiful
3. .NET eCommerce components can be written in any Microsoft .NET-compliant language (VB.NET, C#, etc.) and can be used on any Microsoft .NET website
4. A number of companies are producing quality Microsoft .NET eCommerce components that shorten development time

If you are considering .NET eCommerce development, consider the following:

Action Steps
The best contacts and resources to help you get it done

Download Microsoft .NET software

It is hard to begin thinking about Microsoft .NET eCommerce development without having Microsoft .NET. Developers need the entire Microsoft .NET framework and development tools, but you are only installing an already existing application, you will only need the CLR (Common Language Runtime).

I recommend: Download the Microsoft .NET Framework or the CLR. Given the popularity of the software, it is hosted on many non-Microsoft sites such as BrotherSoft.com, which offers the latest version of Microsoft.NET, or Download.com, which offers a number of different versions and the CLR. Also, you can download Express versions of all Microsoft development tools.

Evaluate third party Microsoft .NET eCommerce products

You will need to decide how much, if any, of your .NET eCommerce site's functionality will come from third party .NET components and how much you will be designing in-house. Most .NET controls will only cost a few hundred dollars, at most. Others will be free, but may not support the features you need.

I recommend: Before starting your software project, evaluate which components exist in the marketplace. Devexpress.com offers 40 free controls for signing up on their site. Code Beach, on the other hand, has a directory of pay controls you can investigate for your Microsoft .NET projects. Evaluate these controls to see if they do what you want.

Consider training your staff, as .NET eCommerce can be difficult to learn

If you are contemplating the move to Microsoft .NET or if your company has decided it must upgrade to a new version, do not rule out the possibility of training. Parts of Microsoft .NET can be very complex and a little extra knowledge may ultimately save money in the end.

I recommend: SetFocus.com has a series of online courses that can get your staff up to date on Microsoft .NET eCommerce development. Preparing programmers for certification is another way to educate IT staff and can add to the prestige of the company. Go straight to the source: Microsoft certification training.

Tips & Tactics

Helpful advice for making the most of this Guide

• •  If you are choosing between C# and VB.NET, go with C#. Most .NET components and code samples are written in C# and it is a more powerful language.
• •  Many components for .NET can be used in both web and desktop applications. If your company does both types of development, try to find .NET controls that support both environments.
• •  Microsoft .NET components tend to have backwards compatibility issues. Choose a version of Microsoft .NET early on and make sure all .NET components work with that version.