I want to deploy my ASP.NET application. Its not a "web site" it's a web application.
I'm looking 1) The quickest possible thing to do so I can start of testing 2) A more automated approach.
Any ideas?
3
-
What do you mean "web application" not "web site" (VS Project Type?). Where are you deploying to. Are you developing with Visual Studio? Which version? What OS are you running? Can you be more specific with what it is you want to do?NerdFury– NerdFury2009-06-17 14:49:57 +00:00Commented Jun 17, 2009 at 14:49
-
@NerdFury: He obviously means he has a Web Application Project, and not a Web Site "project". It was created via Add->New Project, not Add->New Web Site.John Saunders– John Saunders2009-06-17 14:54:51 +00:00Commented Jun 17, 2009 at 14:54
-
Web application refers to VS project type. Deploying to WIndows Server 2003, IIS 7 Using VS 2008AJM– AJM2009-06-17 14:57:47 +00:00Commented Jun 17, 2009 at 14:57
Add a comment
|
2 Answers
Your fastest manner for getting it ready for testing is from the "Build" menu to select "Publish".
This will pre-compile everything and you can have it deploy to a folder, then set it up in IIS, change the connection string and you are set to go.
To "Automate" that process, you are going to most likely want to look at creating an install package.
answered Jun 17, 2009 at 14:48
Mitchel Sellers
63.3k15 gold badges115 silver badges174 bronze badges
Comments
If you're using MSBuild grab MSBuild community tasks @ http://msbuildtasks.tigris.org/
And take a look at the WebDirectoryCreate task. There are plenty of other task libraries, but this is what I personally use.
If you're looking at changing configuration settings a simple xcopy and a folder naming structure was the simplest solution for me.
The quickest possible way is the publish command and setting up the virtual directory in IIS manually. I personally got sick of that so I went and looked into NANT and MSBuild.
