clickonce

I am using VS 2010. My app is ClickOnce deployed. My three Prerequisites are CR 2010 and both the .NET 4.0's. When i run the ClickOnce the CR 2010 prerequisites runs first, but it requires .NET to be on the machine to be successful. I need this ClickOnce to first install .NET 4.0 THEN CR 2010. Seems like a simply proposition, but one that i cant seem to get answered? Any help would be greatly appreciated! Jim The bootstrapper packages are usually defined here... C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages Under each package it a product.xml file. I think this may be

We have a line of business app which is deployed via clickonce. I can build and publish the application without any problems but when I try to use Continuous Integration (Build each check-in) I get the following error: 2>C:\Program Files (x86)\MSBuild\12.0\bin\amd64\Microsoft.Common.CurrentVersion.targets(3450,5): error MSB4044: The "SignFile" task was not given a value for the required parameter "CertificateThumbprint". [C:\Builds\1\Pulse\DefaultBuild\src\Pulse\Pulse\Pulse.csproj] Done executing task "SignFile" -- FAILED. We sign the application (to be more specific: the ClickOnce manifest)

We are using Mage.exe to generate our application's manifests as part of our build process. Upon upgrading to .NET 4 we now find it generates an invalid manifest. The reason is there isn't a compatibleFrameworks attribute being set in the application manifest which we generate every build. Is there a way we can make Mage.exe add this element or should we only ever update existing manifests? Add this to your GenerateDeploymentManifest MSBuild task TargetFrameworkMoniker=".NETFramework,Version=v4.0" and that should fix it There is a separate copy of mage.exe built for .NET 4.0. Try using this

I have a normal windows forms program (Not VSTO) which deploys using click once. The issue is that loads of user are having problems with random errors generally stating (from the IClassFactory failed due to the following error: 80004005). Im deploying Redemption by changing the mode to "Isolated" which appears to work for some users but not others. The users that arn't working can be fixed by manually installing the Redemption DLL. Can anyone explain how to automate the process (I really want it to be reg free so users don't need admin permission to install). Thanks Ross Got this resolved.

I'm using ClickOnce to deploy my application. When the app runs the first time, if a db doesn't exist, it creates one. Problem is, when I update, it removes the local database. Is there a way to tell it to ignore it? I imagine you're putting it in the applications directory... don't! Put it in Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData or Environment.SpecialFolder.LocalApplicationData) . Don't include the database in the deployment. Implement your own db creation (using script) when the database isn't present. In the project's Publish options, under Application Files,

I have a c# ClickOnce application that I need to be able to publish multiple times for OEM purposes. The way I understand it now is that publish settings are located in the .csproj file. However, this is inconvenient in the case where I want to publish multiple versions. for example, Company A needs totally different icons, start menu location, product name etc. from Company B, but the assemblies need not be renamed. Here are a couple approaches/questions that I can think of to solve this issue... 1.Is there a way to create a separate publish settings file to use during build time? 2.Can I