clickonce

I have a .net cf 3.5 Windows Mobile application that my client wants to have autoupdate features. Here is what I have so far: create a CAB using the Smart Device CAB Project (is this good enough, or should I be doing something else here) 2.Get the application version number Assembly.GetExecutingAssembly().GetName().Version.ToString(); Call a WCF web service for to do a version number look up. Download a new version of the cab file. ??? Execute WCELoad.exe on the CAB file Profit Your solution is generally correct, but has a few problems. You can't update yourself. You have to shut down and have

Is there a way to automatically increment the "minimum required version" fields in a ClickOnce deployment to always equal the current build number? Basically, I always want my deployment to be automatically updated at launch. I suspect I'm going to need a some pre-/post-build events, but I hope there's an easier way. I may be a little late with answering this one but I found it difficult to find the solution on google but eventually figured it out so thought I would share. With MSBuild version 4 (VS2010 and VS2012) this can be achieved by inserting the following target: <Target Name=

I have a CruiseControl .NET build server running on Windows Server 2003, and I am trying to build and publish my ClickOnce application using msbuild. Everything is working fine, except when I enable the bootstrapper of my ClickOnce application. When this happens, I get the following error in the DeploymentGenerateBootstrapper target: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3939,9): error MSB3147: Could not find required file 'setup.bin' in 'E:\Projects\src\TestProject\Engine'. .NET Framework 3.5 SP1 and 4 and latest Windows SDK for both are installed on the

If one will release a ClickOnce version, how can it be obfuscated by Dotfuscator ? You can use the commercial version of Dotfuscator to automatically obfuscate a ClickOnce application by adding the deployment manifest ("foo.application") as an input to your Dotfuscator project. Dotfuscator will allow you to add any necessary exclusions to the assemblies contained in the ClickOnce application and will create updated deployment and application manifests containing the obfuscated assemblies. The free version of Dotfuscator included in Visual Studio (including Visual Studio 2010) does not have the

Is anyone using ClickOnce with VS2010? I’m getting the following on publish, when the solution builds fine ... Building WindowsFormsApplication1... Error: Cannot publish because a project failed to build. Have tried everything, new clean project (both windforms and WPF), new temporary key, disabled pre-requisites and played with every publish setting. I was hoping it’d be fixed in final, the same thing happened in RC My 'workaround' at the moment is to use msbuild.exe with a clickonce.proj, along the lines of the following http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/40bb7d32

I'm wondering if you can create a ClickOnce installer for a project and then host the installation folder on GitHub (via the downloads page)? I guess by default ClickOnce publishes the installation files to a subfolder which I think is not supported on the Github downloads page but maybe there is another way. Yes you can. And actually I think it's a more convenient way comparing to FTP. Make sure your Git is set to "commit as-is", so that you can avoid some signature issues. Publish your ClickOnce application to a directory in your git repository (you may want another branch for that) with the

Since ClickOnce installs per profile rather than per computer, is there any way to uninstall a single ClickOnce client application from multiple profiles at the same time? We have a ClickOnce application that we would like to remove and re-install using a standard MSI , but we don't want to have to log in as each user to do the uninstall. Assuming there isn't anything baked in, is there a custom tool? You could manually delete the ClickOnce install for each user. I haven't tried doing this on a large scale, so use at your own risk. However, these steps should get rid of a ClickOnce app. Delete