clickonce

问题 I've been trying to disable the DPI awareness on a ClickOnce application. I quickly found out, it is not possible to specify it in the manifest, because ClickOnce does not support asm.v3 in the manifest file. The next option I found was calling the new Windows function SetProcessDpiAwareness. According to this tutorial, Call SetProcessDpiAwareness before you create the application window. And this tutorial, you must call SetProcessDpiAwareness prior to any Win32API call You have to call the

问题 I have a distributed application via ClickOnce. I updated several times and there has never been a problem. Since the last update (which was minor: a label), when I run my application from a post, click once start and prompt me an error: Application Cannot Be started When I look at the logs I get the following message: OPERATION PROGRESS STATUS * [04/10/2012 13:24:33] : Activation of C:\Users\xxxxxxxxx.appref-ms| has started. * [04/10/2012 13:24:33] : Performing necessary update check as

问题 I am using ClickOnce to distribute an application from a website URL. The application has a few merge modules such as ADO ActiveSync that requires the ClickOnce installer to download the dependecy. If I password protect the URL, the user can log in and start the Click Once process using the publish.htm page. The process fails when it tries to download the dependecy files since ClickOnce is not supplying the authentication information. Is there a setting I can use so that ClickOnce can log

问题 I have a click-once application, which is correctly signed, correctly configured and installs itself without any problem. It is set to run offline, but install from a specific URL, and if I download and run the setup.exe, it installs updates. So, it's basically all working... except I cannot print out the version number, or trigger an update from in code. If I try, I get the dreaded: 'Application identity is not set.' 2017-01-10 13:43:14.8367 ERROR System.Deployment.Application

问题 Inside Visual Studio 2010, I've set my application to target version 4 of the .NET Framework and for "All CPUs". As some of our users are 64-bit while others are 32-bit, I assume one would choose All CPUs. Is that correct? On a particular user's 32-bit Windows 7 SP1 machine, the framework installation (via ClickOnce) is failing with an error code 5100, which according to this MSDN article, indicates that The user's computer does not meet system requirements . The user's PC is 32-bit Windows 7

问题 I have a relatively simple support application which I have chosen to deploy to our support staff via click once. I assume it's still called Click-Once. I'm using the publish tab of the project's properties in VS2008. Several users have managed to click through to the url, download and run the application. One specific user cannot. He has .Net 3.5 SP1 installed and indeed reaches the publish page where he is offered the option to install. upon clicking this he is greeted with an error message

问题 I have a ClickOnce application (app1) that calls DLL files from another solution (app2). I recently updated this application at one customer and a strange thing occurred. He got the new version (publish version was correct in Control Panel / Add or Remove Programs ) of app1 and the application version was correct as manually inspected in the application. But the DLL files called from the referenced solution (app2) was still the old ones. We deleted all files in C:\Documents and Settings

问题 I am using ClickOnce to deploy a C# application. It is available online only, so I cannot disable the application to check update every time it starts. Every time when it gets launched from url, you will see a "verifying application requirement" window. This is fine. However, the time it takes for this window to disappear varies greatly. Sometimes it's instant, sometimes it takes a few seconds. Anyone know why this is the case and how to speed up this verifying process? I am using process p =

问题 What is the proper way to set the Company Name and Application Name in a ClickOnce application? I have a set of projects in a solution called RecordNavigator. The GUI project is called RecordNavigator.Gui. When I publish the application - I want the Start menu to have a folder called Tyndall Software and the application shortcut to be called Record Navigator . Right now the folder says Organization and the shortcut says RecordNavigator.Gui . The AssemblyInfo.cs file seems to have no effect.

问题 When I try to access "Application.CommonAppDataPath" i get this error message: System.Deployment: Store metadata "CurrentBind" is not valid Stack Trace: at System.Deployment.Application.ComponentStore.GetPropertyString(DefinitionAppId appId, String propName) This is only in Debug. When running as an actual published clickonce application it works fine. How can I get rid of this exception when debugging locally? 回答1: I had a similar issue (like jpierson's comment) with the same exception '