Understanding the .NET Framework

(Page 1 of 8 )

To better understand developing applications using ADO.NET, this chapter from ADO.NET: The Complete Reference by Michael Otey and Denielle Otey (McGraw-Hill/Osborne, 2003, ISBN: 0-07-222898-9) introduces the .NET architecture. Because few applications are stand-alone database applications that just need to access database resources and nothing else, you'll also need to know which of the .NET Namespaces to include in your applications to enable access to other system resources.

Before launching into building ADO.NET applications, it's good to have a solid understanding of the new Microsoft .NET Framework. The .NET Framework is Microsoft's new development platform that brings with it enormous changes in the nature of the applications that are developed, as well as the development tools and methodologies that are used to develop those applications. To help you get a more complete understanding of the applications that you develop using ADO.NET and the Microsoft .NET Framework, this chapter starts out with an introduction to the new Microsoft .NET architecture, where you'll learn about the Common Language Runtime (CLR) and the Common Type System (CTS). The next part of this chapter provides a general overview of the major Namespaces in the .NET Framework. Very few applications are stand-alone database applications that just need to access database resources and nothing else. In order to access other system resources, you need to understand which of the .NET Namespaces you need to include in your applications. Next, you'll get a more in-depth look at the anatomy of programs (aka assemblies) that are created when you build .NET applications. Understanding the context of the .NET assemblies can help you understand the deployment issues that are encountered when deploying .NET applications.

The .NET System Requirements

The first thing you need to know about .NET applications is where they can run. In this section, you can see the hardware and software requirements for .NET Client and .NET Server applications.

Hardware Requirements

Table 2-1 lists the .NET hardware requirements. These hardware requirements are divided into requirements for client/desktop applications, as well as server-side ASP.NET applications. This table lists the Microsoft minimum and recommended system specifications. In typical Microsoft fashion, they've low-balled their hardware recommendations. Although .NET applications may run in these low-powered systems specified in the minimum columns, in my experience, you'll be a lot happier with a faster system. We've included a "Better" column indicating a more desirable system specification. But bear in mind that, like most computer systems, "more is better" and you'll definitely get a better .NET experience running .NET applications on faster hardware.

Platform	CPU	CPU	CPU	RAM	RAM	RAM
	Minimum(MHz)	Recommended(MHz)	Better(MHz)	Minimum(MB)	Recommended(MB)	Better(MB)
.NET  Client	90	90+	350+	32	96+	128+
.NET Server	133	133+	450+	128	256+	512+

Table 2-1. .NET Hardware Requirements

Operating System Requirements

In addition to the hardware requirements, .NET applications also have a minimum required operating system level to support the various .NET features. Table 2-2 shows the .NET Framework software requirements.

Platform	Operating System	Additional Software
.NET Client	Windows 98
	Windows 98 SE
	Windows ME
	Windows NT 4.0 Workstation	Service Pack 6a
	Windows NT 4.0 Server	Service Pack 6a
	Windows 2000 Professional
	Windows 2000 Server
	Windows 2000 Advanced Server
	Windows 2000 Datacenter Server
	Windows XP Home Edition
	Windows XP Professional
.NET Server	Windows 2000 Professional	Service Pack 2
	Windows 2000 Server	Service Pack 2
	Windows 2000 Advanced Server	Service Pack 2
	Windows 2000 Datacenter Server	Service Pack 2
	Windows XP Professional
	Windows 2003 Server Family

Table 2-2. .NET Operating System Requirements

Database Access Requirements

In addition to the previously mentioned hardware and software prerequisites, certain database access features used by the .NET Framework have minimum MDAC (Microsoft Data Access Components) levels that are required (see Table 2-3). MDAC is included in the installation process for the .NET Framework and Visual Studio.NET, so you don't need to worry about it in a development environment. However, you do need to be concerned about this when you deploy your client and server applications. You can download the Microsoft MDAC support from http://www.microsoft.com/data.

Platform	Middleware	Notes
.NETClient	MDAC 2.6	Needed by the SQL Server .NET Data Provider
.NETServer	MDAC 2.7	Needed by the SQL Server .NET Data Provider

Table 2-3. NET Database Access Requirements

This is chapter two of ADO.NET: The Complete Reference, by Michael and Denielle Otey (McGraw-Hill/Osborne, ISBN 0-07-222898-9, 2003). Check it out at your favorite bookstore today. Buy this book now.

Next: The .NET Architecture >>
 

More .NET Articles
More By McGraw-Hill/Osborne

Comments On: Understanding the .NET Framework

>>> Be the FIRST to comment on this article!