Though installing the .NET Framework is relatively straightforward, there are a couple of questions
raised on the subject:
What version should I install?
What are the system requirements?
Let's take a closer look at each of these points.
What Version Should I Install?
The .NET Framework is currently available in two flavors supplied free for download from
.NET Framework Redistributable (dotnetredist.exe, 21 MB)
.NET Framework Software Development Kit (SDK) (setup.exe, 131 MB)
Although you can develop and run ASP.NET applications with any version, it is recommended that
you install the Redistributable version on your production server where your site is publicly hosted
and install the SDK version on your local development system. There is nothing to stop you from
installing the SDK version on your production server, but under normal circumstances the
production server is only required to provide the runtime environment for your ASP.NET
applications, so it does not need the SDK's documentation or development tools. Some readers
won't need to worry about the production server at all, as the company providing the hosting
services will control this. By installing the SDK version on your development machine, you will
gain the benefit from a vast wealth of documentation, compilers, development tools, and sample
What Are the System Requirements?
The .NET Framework can be installed and used by .NET applications with the following operating
Windows NT 4.0 (SP6a)
Windows Millennium (ME)
Windows XP Professional
Windows XP Home Edition
To build or run ASP.NET applications, the following additional requirements or constraints apply:
Microsoft Internet Explorer 5.01 or later.
Microsoft Data Access Components 2.7 (MDAC) is recommended. A free installer is
available from http://www.microsoft.com/data. MDAC is used to allow programs and
components such as the .NET Framework to access information in databases. It is worth
noting that you can also obtain MDAC 2.7 as part of the Windows XP Service Pack 1 (SP1).
Internet Information Services (IIS) version 5.0 or later (fully patched prior to installing the
.NET Framework). You can determine if your system requires any patches (and also obtain
them) at the Microsoft Windows Update web site: http://windowsupdate.microsoft.com.
ASP.NET is only supported on the following operating systems: Windows 2000 and
Windows XP Professional. Also, it will come preinstalled with Microsoft Windows .NET
Server. Only these operating systems include a compatible web server to run ASP.NET.
Once you have verified that your system is ready to accept installation of the .NET Framework and
you have downloaded the version of your choice, installing it is as simple as running the
downloaded installer file and following the on-screen prompts.
Microsoft .net consulting :
How Can I Fix a Broken .NET Framework Installation?
A common cause of the .NET Framework breaking down occurs when you have to reinstall IIS for
some reason not directly related to the .NET Framework. Doing so removes references to certain
files and services that the .NET Framework configures within IIS during its initial setup. Once these
references have been removed, IIS does not recognize the .aspx file extension used by ASP.NET
pages, causing ASP.NET applications to fail. There are two options for resolving this issue:
Use the aspnet_regiis.exe tool.
Reinstall the .NET Framework.
You can use the first option if you have installed the SDK version of the .NET Framework or have
Visual Studio .NET installed. Details on how to use this tool can be found at
If you only have the .NET Framework Redistributable version installed, the only option is to
reinstall the .NET Framework.
What Does the Error "Access is Denied ‘some.dll’" Mean?
At some stage you may start to randomly receive this error, where some.dll will be the name of a
.NET assembly (DLL file) in the bin folder of your ASP.NET application. This is normally caused
by the Index Server maintaining a lock on the assembly file in question. The best solution is to
disable the Index Server.
To disable the Index Server, perform the following steps:
1. Go to Windows > Control Panel > Administrative Tools, and then click Services.
2. Locate Indexing Service in the list of services and double-click it to open the Properties
3. On the General tab of the Indexing Service Properties dialog box, in the Startup type drop-
down item list, click Disabled.
4. Click OK to exit.
If disabling the Index Server is not an option because you need to use it, you will have to exclude
the Temporary ASP.NET Files folder from Index Server scans. To do so, perform the following
1. Go to Windows > Control Panel > Administrative Tools and click Computer Management.
2. Expand the Services and Applications node, then expand the Indexing Server node, and then
expand the System node.
3. Right-click the Directories folder, point to New, and then click Directory from the subform
to open the Add Directory dialog box.
4. Click Browse, and then select the Temporary ASP.NET Files directory normally found in
c:\<WINDIR>\Microsoft.NET\Framework\v1.0.3705\Temporary ASP.NET Files.
5. Under the Include in Index? option button, click No. Finally, click OK to close the dialog
6. Close the Computer Management dialog box, then stop the Indexing Services service by
right-clicking the Indexing Services node and selecting Stop from the pop-up menu. Then
restart it by selecting Start in the same pop-up menu.
Note <windir> refers to the location of your Windows installation folder. This is normally found in
c:\winnt, but if your Windows 2000/XP installation was installed as an upgrade to Windows
95/98/ME, then the Windows installation folder location could be c:\windows. The
installation folder for the .NET Framework can also change depending on the installed
version; yours may not be named v1.0.3705.
Microsoft .NET Outsourcing | Software outsourcing company | Global delivery model