I've been hired to install an ASP.NET application onto a client’s web server. Usually when I am asked to install my web app onto a client’s web server, the server has been running successfully for a while; serving up pages and doing all of the web server activities it should. In other words the server has been "burned in" a little bit.
Well, in this particular situation, the company has hired "some tech" from "some company" to setup the Server 2003 box that will be running my app and the database that my app uses. IIS and ASP.NET are installed so that is good but I need some help. I find it strange that the 'inetpub' folder isn't created while all of this other setup has been done.
I am not a Server 2003 expert by any means, I know a little but just enough to mess things up.
Information about my web application
Written for using ASP.NET 3.5
Uses MSSQL for database (database seems to be working without problems)
This application will be running in an intranet environment
Questions about server setup
- What should I check on to make sure that this server is ready to run my web app?
Web Service Extension
- Why doesn't the c:\inetpub folder exist?
- What is the best way to install my web app onto this server?
I have added sites manually but that usually ends up with me tinkering around
for a couple of days with settings trying to get my app to run.
- Is there an effective way for me to utilize the web app install wizard?
- Are there other questions that I should be asking?
Thanks for your help.