I use the new VS 2010 configuration transformations to deploy websites. To replace a single setting of my ApplicationSettings I use the following configuration transformation:
I’ve deployed to a server a web application that uses NHibernate. The application compiles and runs fine on my local dev machine, but there’s an issue with NHibernate on the new server. I get the following error:
I am looking for different techniques/tools you use to deploy an ASP.NET web application project (NOT ASP.NET web site) to production?
Anyone have any good tips on handling differences in web.config settings between environments? I’ve considered creating a ‘config’ folder in our source control system but outside of the web hierarchy, and having the deployment process copy the appropriate config files (web.dev.config,web.staging.config, web.production.config) into the web folder upon deployment. I’ve also seen posts on how to programmatically change the config settings (WCF endpoints, connection strings, etc) when the app starts.
For ASP.Net application deployment what type of information (if any) are you storing in the machine.config?
I need to deploy a web application on several laptops (although it is a web application, it is intended to run via localhost only – thus the need to deploy on several different machines).
I’ve finished simple asp.net web application project, compiled it, and try to test on local IIS. I’ve create virtual directory, map it with physical directory, then put all necessary files there, including bin folder with all .dll’s
In the project settings, build section, output path is bin
So when i try to browse my app i got:
Is there a way to set MSDeploy parameters in .csproj file itself of ASP.NET MVC project? Particularly a “skip” parameter, which should skip a “Temp” folder.
How can I deploy an asp.net application to the root of an IIS6 webserver? All the applications I’ve deployed before have been in directories, such as http://www.example.com/app1/. To deploy that for the first time, I’ve always just gone to the IIS manager, and selected “Create Application” in the properties for that folder.
After completing the ASP.NET MVC 3 tutorial (find here), I tried to publish the app online. I contacted the hosting company to be sure if it’s possible to host MVC 3 apps. I had to bin deploy the (dll files) application. So after following some steps on hanselmans blog, I’m getting stuck on following error: