Member Avatar for maurya_alld

Hi,
Can any body tell me step by step, how to upload an asp.net site at booked domain.

Regards
Maurya

  • 3 Contributors
  • 2 Replies
  • 117 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by ukerbel

Dani AI

Generated

Short primer that fills gaps in the replies from and — the two quick things most beginners miss are: (1) pointing the domain name at the hosting server, and (2) the server-side binding and file-permission details that let IIS serve your files reliably.

Typical minimal workflow

  1. Pick a Windows host or VPS that supports the .NET version your app uses and get the server IP/hosting control panel credentials.
  2. Update the domain DNS (usually an A record to the host IP; add a CNAME for www if you use it). DNS changes can take hours to propagate.
  3. Publish from Visual Studio using Web Deploy when available (or FTP if not). Precompile/publish so only the compiled DLLs and static files go up — do not rely on source files on the server. See Web Deploy options for details.
  4. On the server (or in the host control panel) create/assign the site and set the host-name binding so IIS answers for your domain.

Key server configuration notes

  • Use an application pool configured to the correct CLR (or to No Managed Code when proxying ASP.NET Core to Kestrel). For modern app pools prefer the built-in ApplicationPoolIdentity and give that identity NTFS access to the site folder (especially App_Data and bin) — e.g. grant IIS APPPOOL\YourAppPool Modify rights. More on app-pool identities here.
  • Ensure any required Windows components or .NET frameworks are installed on the host. If the host is shared, use the provider’s tools to assign the domain to the site.

Troubleshooting pointers

  • Test before DNS changes by editing your local hosts file to map the domain to the server IP.
  • If you see 403/404/500 errors, check IIS logs, Failed Request Tracing and the Windows Event Viewer; temporarily set customErrors to show detailed errors for debugging (turn it off in production).
  • Verify database connectivity, firewall rules for ports 80/443, and that required assemblies are in bin.

If the host supports Web Deploy, it simplifies updates and permissions; otherwise FTP plus careful NTFS permissions and correct bindings will get a site live.

Recommended Answers

All 2 Replies

Member Avatar for ericstenson

You will need a server running IIS with the ASP.NET extensions. You can either go hosted or set one up yourself.

After that, build the site in VS to the /inetpub/wwwroot folder

Make sure ASP.NET version # is correct in the IIS Website properties and also make sure permissions are set properly.

Not really too hard...

Member Avatar for ukerbel

Visual Studio has a fantastic 'Publish Web Site' option under the Build menu. It's super easy to use and has some properties you can play with. The biggest challenge most people find is the security permissions on their application folder on the server. Just make sure that you set that up properly.

MSDN has a good step-by-step article which can be found at: (VS.80).aspx

Good luck!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.