clickonce

According to Microsoft , you must sign your ClickOnce application. But it seems to me that it works just fine when I publish it without signing it (by turning off the 'Sign the ClickOnce manifests' option). I really didn't care and kept the default values (I think I was using a test certificate) until I changed computer and started getting a message telling me that 'The application is signed with a different key than the existing application on the server', which seems will cause my users to stop getting automatic updates. Apparently, VS uses my computer's name to create the key. So, should I

We have a vendor application that we extend and deploy via ClickOnce. The vendor also provides a 'Deployment Manager' which packages the app and any extensions into a ClickOnce deployment that we publish to a web server. I mention this detail so that it's understood we don't really have great control over changing the deployment process. So, we publish the application to our web server. That works fine, and updates work correctly. On loading the application, it will prompt the user if they want to update the application. Several of our clients have asked for an 'MSI installer'. Their users

I've created a Windows C# project and made it as ClickOnce Application(Publish feature in Project properties) for Installation. I want to Include a folder which has Crystal Report (rpt) files in it. In my application I have given path of rpt file as my Installation location. How can I include this folder while publish. So that I need not copy the folder manually. You have to add the items to the project and mark them as 'Content' (select the item in solution explorer, right click, properties, set Build Action). So Tom has explained how to add a file. You specifically say you would like to add

I've been really struggling with this one for days. I've seen other posts like ClickOnce Deployment Error: different computed hash than specified in manifest , but the solutions do not seem to work for me. I have a valid code signing certificate, and have been using it to sign my ClickOnce application for months. I realized I wasn't signing the executable and dlls themselves, so I attempt to do so. Now every time I publish and run the setup.exe, it fails with: "File, xxxxxx.dll, has a different computed hash than specified in manifest." If I do not sign the exe and Dlls, I can redeploy. I made

I have a simple batch file that I'm running from a DOS command line that is used for building a small C# application that publishes a ClickOnce project. One line is this: msbuild MyApp.csproj /t:publish /property:PublishDir="deploy/" This currently publishes the application, but it uses the Publish Version that I set up in Visual Studio's "Publish" tab. I'm hoping to be able to set the publish version at the command line, and specifically, I'd like to use the Assembly Version of the project. Something like: msbuild MyApp.csproj /t:publish /property:PublishDir="deploy/" /property:PublishVersion

I've created a custom setup package to install some fonts on a client machine and deployed it to the prerequisites folder under C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\FontsInstaller . Everything is fine with reference it as a prerequisite in Visual Studio 2010 and I am able to publish the application without issue. The client on the other hand gets an error during the Hash verification: Verifying file hash Error: Setup has detected that the file 'C:\Users\RMORAN~1\AppData\Local\Temp\VSD4684.tmp\FontsInstaller\fontsinstaller.msi' has either changed since it

We recently upgraded Visual Studio from 2010 to 2013 and everything seems to be working the same as before except for one thing. In 2010 code signing was only performed when publishing the project, but in 2013 it wants to sign the output assembly every time we build the project. I'm having issues trying to find any results online about this, everything only points to how to setup signing in the first place, not how to prevent it signing during normal debug builds. I created a new project and started playing with the settings to determine what single setting may be triggering the signing

A common technical decision nowadays is whether to build a ClickOnce rich client application or a web application. Here I'm focussing primarily on choosing between a WPF application or a Silverlight application. The chief benefit of Silverlight is obvious - it can be hosted in a browser. But, if a programmer used to WPF was to start programing in Silverlight, what would he/she suddenly find is not possible or much harder? Items can be of the following: You just cannot do it, period You can do it, but only sort of, with lots of caveats You can do it, but there's a lot more hoops to jump through