Hi Friends - Dot net installation steps - very urgent

A compact, practical checklist to get Visual Studio 2005 -> ASP.NET (2.0) -> SQL Server 2005 running under IIS. This complements @ravichandra’s uploaded video and answers @namsSoftee’s question about virtual directories and whether VS2005 uses the same steps as VS2003.

1. Prepare the machine

   • Install IIS (enable the Web Server feature on the OS) before you deploy.
   • Install SQL Server 2005, choose authentication (Windows or Mixed), create your DB and login.

2. Install Visual Studio 2005

   • Include Web development components. If you prefer the old VS2003 single-assembly model, install VS2005 SP1 (or the Web Application Projects add-on) to get the Web Application Project behavior.

3. Register ASP.NET 2.0 with IIS (run elevated)

%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
iisreset

1. Create the site/application in IIS

   • In IIS Manager create a Virtual Directory (or site), then click Properties -> Create to make it an Application.
   • Assign an application pool that targets .NET v2.0.50727.
   • Set Execute Permissions to Scripts (or as required).

2. File/DB permissions and deployment

   • Grant the app pool identity (NETWORK SERVICE on older IIS, ApplicationPoolIdentity or specific account on newer IIS) read/write to App_Data and any folder you need write access to.
   • Update web.config connectionStrings to point to your SQL Server and deploy files into the virtual directory.

Differences VS2003 vs VS2005

• VS2003 targets .NET 1.1 and traditionally auto-created virtual directories. VS2005 targets .NET 2.0 and introduced the Web Site model (File System by default). If you choose “HTTP” when creating a Web Site, VS2005 can create the IIS virtual directory for you—run Visual Studio elevated when UAC is present.

Common troubleshooting

• If you see 500 errors, verify the app pool .NET version, run aspnet_regiis, check Event Viewer, and temporarily set customErrors="Off" to see details (do not leave this on in production). For 404 on default pages, confirm Default Document settings and that the virtual directory is an Application.

For details on registering ASP.NET with IIS see the Microsoft aspnet_regiis.exe documentation: aspnet_regiis.exe tool.