I had to work through the signed ClickOnce recently. It was not the most smooth experience, but once this has been done (and wired to the automated publishing) it started working like a marvel. Here’s the actual product, if you are interested in the behavior: Forecasting Add-in for Excel. Article on ClickOnce Manifest Signing and … Read more
You enjoyed my answer in the MSDN Forums so much, I’m posting the link to the answer here as well. 😉 If you are publishing and installing from the same URL, you can just fill in the publishing file location and be done. The reason there are two is so if you want to publish … Read more
We use Team Foundation Server Team Build and have added a block to the TFSBuild.proj’s AfterCompile target to trigger the ClickOnce publish with our preferred version number: <MSBuild Projects=”$(SolutionRoot)\MyProject\Myproject.csproj” Properties=”PublishDir=$(OutDir)\myProjectPublish\; ApplicationVersion=$(PublishApplicationVersion); Configuration=$(Configuration);Platform=$(Platform)” Targets=”Publish” /> The PublishApplicationVersion variable is generated by a custom MSBuild task to use the TFS Changeset number, but you could use your … Read more
I found solution here: “Unable to install or run the application. The application requires that the assembly be installed in the Global Assembly Cache (GAC) first.” Excerpt from wordpress link: I recevied this error while compiling my first C# production application. I had to do the following in Visual Studio for the project: In Solution Explorer, … Read more
Here are a few that I am aware of. Can’t put an icon on the desktop. You can now. I can’t install for all users. I need to jump through hoops to move the deployment to a different server. It is not a problem if you are developing internally, and the users can see the … Read more
If you’re after a quick solution, then you can “renew” your existing certificate and just give it a longer expiry date. Cliff Stanford has cleaned up the Microsoft “workaround” and made it available as a simple command line exe – available here: http://may.be/renewcert/ – Nice work Cliff !
Funnily enough, publish from right-click on the project menu seems to work. It fires up the wizard rather than just publishing, so not ideal, but I do have 2 workarounds now (including the one stated in my original post).
Visual Studio isn’t needed, just Mage. It comes with the Windows SDK for people that haven’t gotten it via Visual Studio or the Framework SDK. Another option would be to write code to clear the cache. Or you could have them delete the folder ClickOnce files are installed in (C:\Users\[username]\AppData\Local\Apps on my Windows 7 machine). That … Read more
It might sound kind of lame, but the easiest way to do this is to have two EXE projects in your solution. The Main method of each of these will just call the Main method in your original EXE project (which you’ll have just switched over to being a DLL file). This means that each … Read more
sylvanaar’s last line looks like the way to go, in my experience; but with the caveat that it is only available to deployed versions of the application. For debugging purposes, you might want something like: static internal string GetVersion() { if (ApplicationDeployment.IsNetworkDeployed) { return ApplicationDeployment.CurrentDeployment.CurrentVersion.ToString(); } return “Debug”; }