CODEWITHSUNDEEP
msbuildclickonce
Gab
Gab

Reputation: 1910

Creating ClickOnce Applications for Others to Deploy

I have a WPF application and I'm creating a ClickOnce deployment from my continuous integration server (TeamCity) with a MSBuild command.

Then I would like to give the deployment files to others, so they can modify the URL in the .application file by their own server address where they want to host the files.

The problem is that the .application file cannot be simply modified like this. It has to be resigned...

Is there a simple way to do what I need without resigning the .application file ?

I found this link and this tutorial but I'm not using Mage.exe for my deployment. And What should I do after the deployment MSBuild command to do what I need ?

My parameters :

/P:Configuration=Release /P:Platform="x86" /P:DeployTarget="Publish" /P:SupportUrl="http://www.company.com" /P:ErrorReportUrl="http://www.company.com" /P:PublisherName="company" /P:ProductName="Product name" /P:TrustUrlParameters="true" /P:UpdateMode="Foreground"/P:PublishUrl="http://localhost/Installer/" /P:UseManifestForTrust="true" /P:MapFileExtensions="true" /P:PublishDir="../../Installer/" /P:ApplicationVersion=%Version%

The application should be able to be updated.

Upvotes: 2

Views: 1061

Answers (1)

Ilya Kozhevnikov
Ilya Kozhevnikov

Reputation: 10432

You can drop the deploymentProvider element; that would allow you to deploy a signed ClickOnce from multiple locations, i.e. multiple environments or multiple organisations in your case.

http://msdn.microsoft.com/en-us/library/bb384243.aspx

Starting with the .NET Framework 3.5, you no longer have to specify a deploymentProvider in your deployment manifest in order to deploy a ClickOnce application for both online and offline usage. This supports the scenario where you need to package and sign the deployment yourself, but allow other companies to deploy the application over their networks.

Upvotes: 1

Related Questions