clickonce

问题 I have a visual basic project that is being published and increments the version number each time. When I install a new version, it opens but as soon as the application restarts, it seems to revert back to the previous version and I cannot work out why. 回答1: Try to update a minimum version required when you publish the application go to application proprties -> publish -> Updates...: If you want to do this automatically and force the user to work on latest version only, you can update the

问题 I have a visual basic project that is being published and increments the version number each time. When I install a new version, it opens but as soon as the application restarts, it seems to revert back to the previous version and I cannot work out why. 回答1: Try to update a minimum version required when you publish the application go to application proprties -> publish -> Updates...: If you want to do this automatically and force the user to work on latest version only, you can update the

问题 This question describes my problem exactly, except I'm using a custom configuration section in app.config with ConfigurationManager , so the solution presented there doesn't apply... Basically, my problem is that when ClickOnce updates the application, it installs into a different directory with the new app.config, thereby erasing any changes made. My application uses app.config to persist application settings, so this is very bad... a merged update would be excellent (similar to what is

问题 Release an HelloWorld add-in for Ms Word. Sign and publish via ClickOnce, with the installation folder being set to an online directory. Routine to follow Run the add-in setup.exe to install via ClickOnce. Assert the add-in has been registered in File / Options / Add-ins . Close Word. Go to the Programs and Features panel, and uninstall the ClickOnce application which corresponds to the Add-in. Launch Word and assert the add-in has been unregistered from File / Options / Add-ins . Run the add

问题 I develop VSTO solutions for Word and Excel. Since yesterday, for no apparent reason, I am now unable to debug any of my solutions. I face the same symptoms even when I try to debug a new blank VSTO project. When the add-in launches (typically at Excel or Word startup), the following shows up: System.Security.SecurityException: Customized functionality in this application will not work because the certificate used to sign the deployment manifest for ExcelAddIn1 or its location is not trusted.

问题 I am working on deploying a ClickOnce Application build on .NET 4.5 Here are the facts: I have a valid Comodo Authenticode Certificate The certificate is installed in my local cert store The project properties for "Signing" tab show that the certificate should be used for signing the manifest (I'm not even yet trying to sign the Assemblies for .NET) The proper timestamp server URL is entered for comodo On the Publish tab, the settings are very typical: Publish to a UNC path Installation

问题 I am working on deploying a ClickOnce Application build on .NET 4.5 Here are the facts: I have a valid Comodo Authenticode Certificate The certificate is installed in my local cert store The project properties for "Signing" tab show that the certificate should be used for signing the manifest (I'm not even yet trying to sign the Assemblies for .NET) The proper timestamp server URL is entered for comodo On the Publish tab, the settings are very typical: Publish to a UNC path Installation

问题 We are evaluating the migration from our current client/server application to .NET Core. The 3.0 release added the support for WinForms we need for our client, but ClickOnce will not be supported. Our solution is installed on-premise and we need to include settings (among others) like the address to the application server. We create dynamically ClickOnce packages that can be used to install and update the clients and include the settings. This is working like a charm today. The users install

问题 We are evaluating the migration from our current client/server application to .NET Core. The 3.0 release added the support for WinForms we need for our client, but ClickOnce will not be supported. Our solution is installed on-premise and we need to include settings (among others) like the address to the application server. We create dynamically ClickOnce packages that can be used to install and update the clients and include the settings. This is working like a charm today. The users install

问题 We have a Windows Forms, .NET 2.0 application delivered via ClickOnce and driven by web services, that our customers occasionally wish to deploy into a Citrix environment. In some cases, the customer elects to allow our application to be deployed locally to user machines and bypass the Citrix server, in one case we've provided a static installer for a customer to use with the proviso that updates would not be pushed automatically, and in some cases, our customer IT departments have had the