Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Deploying a ClickOnce application using MSBuild does not create a Deployment Web Page.
 

Deploying a ClickOnce application using MSBuild does not create a Deployment Web Page.

I have a c#application that when I publish it within Visual Studio2008 it creates a deployment web page (Publish Folder --> Options Button --> Deployment section --> Deployment web Page --install.htm-- and have clicked on "Automatically generate deployment web page after every publish"), but when I publish the app using MSBuild (with the intention of automating the deployment of such an app) it does not generate a deployment web page.

When using MSBuild, other options/properties are taken as saved on the project properties, for example "use .deploy file extension" both on and off, incrementing publish version, etc.

Is there any property (or anything else) I can set to make MSBuild create the deployment web page?

(I have read the info on this link: http://msdn.microsoft.com/en-us/library/ms165431.aspxas well as others but have not found an answer).

Thanks in advance to all that respond.
juancamaney  Wednesday, August 05, 2009 9:37 PM
I'm assuming you have the information filled in, in Visual Studio, right?

If so, then I would gather that MSBuild won't create that deployment page for you, it is a function of Visual studio.

Here's your options:

(1) Edit the generated publish.htm and remove the version, then just copy it to your web server and don't replace it.
(2) Edit the generated publish.htm every time you push a new version, and copy it to your web server.
(3) Create your own attractive company-branded publish.htm page with a link to your setup.exe file and put it on your web server.

RobinDotNet
Click here to visit my ClickOnce blog!
  • Marked As Answer byjuancamaney Friday, August 07, 2009 3:38 PM
  •  
RobinDotNet  Thursday, August 06, 2009 6:54 PM
I'm assuming you have the information filled in, in Visual Studio, right?

If so, then I would gather that MSBuild won't create that deployment page for you, it is a function of Visual studio.

Here's your options:

(1) Edit the generated publish.htm and remove the version, then just copy it to your web server and don't replace it.
(2) Edit the generated publish.htm every time you push a new version, and copy it to your web server.
(3) Create your own attractive company-branded publish.htm page with a link to your setup.exe file and put it on your web server.

RobinDotNet
Click here to visit my ClickOnce blog!
  • Marked As Answer byjuancamaney Friday, August 07, 2009 3:38 PM
  •  
RobinDotNet  Thursday, August 06, 2009 6:54 PM
RobinDotNet,

Thanks so much for your answer.

Yes, I have filled in all the information in Visual Studio and also I have published from there (so the settings would 'stick' for my MSBuild). Apparently only certain properties are considered by MSBuild.

What I have done so far is I have created a batch file that after calling MSBuild it would call a C Sharp program to go and figure out therecently created versionand modify the publish.htm accorgingly. Then, I copy it to the web server. Not pretty but it works.

Thanks again.
juancamaney  Friday, August 07, 2009 3:38 PM
That's a great idea. Thanks for posting it back so others can consider it when they run into the same problem.

RobinDotNet
Click here to visit my ClickOnce blog!
RobinDotNet  Friday, August 07, 2009 6:52 PM

You can use google to search for other answers

Custom Search

More Threads

• Installation With Minimum Size
• clickonce over ssl with client certificates
• Installing to a folder depending on which one exists already (different for every language)
• how to deploy a C# application on client machine that does not have .net frame work
• Problems after the setup has finished
• installing .net framework automatically
• Can a custom action restart the install
• Specify Installation Location for ClickOnce deployment
• Quit the Install~
• Problem using auto updater componet