I’ve inherited a very large VS2012 web site project (not web application) and am trying to automate it’s deployment. There are tons of circular references in the project so to get it to precompile using aspnet_compiler.exe I have to turn on fixednames. The problem with that is it causes the build to take about 20 minutes on my quad core, 16gb ram, ssd developer machine. The previous developer didn’t have to deal with this as he would just copy the whole source to the production web server.
So before I tackle the circular references issue I want to at least automatically deploy the project using msdeploy. I can use the publish profiles within visual studio and it does exactly what I want:
- Builds the referenced DLL’s and adds them to the project.
- Does the web.config transforms.
- Does not even attempt to build the website but just packages into a zip file for me.
What I can’t figure out for the life of me is how to get MSBuild.exe to do that exact same thing!
MSBuild.exe WebProject.vs2012.sln /m /T:Build /p:Configuration=Release`;DeployOnBuild=true`;PublishProfile=TestDeploy
The command above still tries to execute aspnet_compiler which is not what I want. The publish profile says that it shouldn’t be precompiled… but in the logs I see it executing it.
So: How can I use msbuild to deploy a Web Site Project without precompiling it?
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
For website project the publish process is not plumbed into the build process. For website project since there is no formal build process there was nothing for us to really extend.
Note: the below contents requires to have VS 2012 (or VS2010 for that matter) and the Azure SDK on top of that. The features were not included in the RTM drop of VS2012.
After creating a publish profile in VS the following are created:
- A publish profile (.pubxml file) under App_Data/PublishProfiles
website.publishprojin the root of the website
The purpose of the
website.publishproj is to facilitate command line publishing. It is a fill in for the
.csproj/.vbproj which you would normally get when using a Web App Project.
If you would like to automate publishing you can use a command like the following.
msbuild.exe website.publishproj /p:DeployOnBuild=true /p:PublishProfile=<profile-name-no-extension> /p:VisualStudioVersion=11.0
You should not have to specify which targets invoked.
Regarding the message in VS that the site is being pre-compiled, that is a bug. It runs through a pre-compile but the publish uses the setting in the profile. That bug should have been fixed in Visual Studio Update 1. After installing that you should not see the un-necessary pre-compile step. Please let me know if you still do see that.
While Sayed Ibrahim Hashimi’s answer did help me somewhat, here is what I found to be neccessary for VS2012:
After installing the Azure SDK, I created a file publish profile, which created a
PublishProfiles folder in the
Properties folder of my project. Inside this new folder, two xml files named
my_sample_PublishProfile_Foo.pubxml.user where created.
Using the .pubxml, I am able to publish with
msbuild like this:
c:WindowsMicrosoft.NETFrameworkv4.0.30319msbuild.exe "C:...UI.csproj" /p:DeployOnBuild=true /p:PublishProfile="C:...PublishProfilesmy_sample_PublishProfile_Foo.pubxml" /p:VisualStudioVersion=11.0
Remember to run the batch file that contains this script with Administrator privileges.