clickonce

SignTool Not Signing ClickOnce App Using SHA256, Only Uses SHA1

Deadly 提交于 2019-11-27 14:57:41
问题 I'm trying to sign my clickonce app. I have an EV code signing certificate that is using SHA256. The problem is that when I sign my app using the post build commands, it seems to be using SHA1 instead of SHA256. Here is a clip of the output window: Running Code Analysis... 1> Code Analysis Complete -- 0 error(s), 0 warning(s) 1> The following certificate was selected: 1> Issued to: Certificate Subject Name Here 1> 1> Issued by: DigiCert EV Code Signing CA (SHA2) 1> 1> Expires: Thu Apr 14 06

Effect of changing ClickOnce application publish location on clients' machines

断了今生、忘了曾经 提交于 2019-11-27 14:47:19
问题 OK, I have a Windows Forms application published using ClickOnce to http://MyDevComputer1/DevPublishFolder/ , so the deployement link is http://MyDevComputer1/DevPublishFolder/publish.htm . The application is already deployed to close to 20 machines in the company intranet. I now have a requirement to change the publish location to a different server in the same network, but I'm just not sure how this change will affect the users who already have the application installed on their client

Deploying WPF Application with 3rd Party DLLs

时光总嘲笑我的痴心妄想 提交于 2019-11-27 14:04:11
I've been extremely frustrated trying to deploy a C#/WPF application I've created that has some references to 3rd party DLLs. I created a folder in the project, called lib , where I placed all of these DLLs. In VS2012, I added the references by browsing to that folder, and selecting all the DLLs. Copy Local is set to true for all. Everything is fine when I build and run, but when I choose publish, and create a OneClick Installer, things aren't so smooth. During the publish wizard, I set it to install from disk, and set it to never check for updates. I take that folder, place it on a flash

How can I prevent launching my app multiple times?

霸气de小男生 提交于 2019-11-27 11:44:08
问题 I deployed my C# WinForms application using ClickOnce installation. Everything works fine with it (after a lot of work) :), but now I'm facing a problem: Whenever I click on the application shortcut in the Start menu, a new instance starts. I need to avoid this. What can I do to prevent multiple launches? 回答1: At program startup check if same process is already running: using System.Diagnostics; static void Main(string[] args) { String thisprocessname = Process.GetCurrentProcess().ProcessName

How to synchronise the publish version to the assembly version in a .NET ClickOnce application?

最后都变了- 提交于 2019-11-27 11:31:31
问题 In my C# ClickOnce application, there is an auto-incremented publish version in the Project -> Properties -> Publish tab. I'd like to display that version in my menu Help -> About box, but the code I'm using apparently accesses the assembly Version, which is different. The Assembly Version can be changed manually in the Project -> Properties -> Application -> Assembly Information dialog. So for now, every time before I publish I've been copying the publish version to the assembly version, so

ClickOnce error: Value does not fall within the expected range

本秂侑毒 提交于 2019-11-27 11:18:24
Getting this error on ALL ClickOnce application launches for a certain user. This started happening after a version upgrade (but happens to no one else). I've tried subsequently changing the version number, add/remove, registry scrub, clearing Local Settings\Apps folder, etc... Still no luck. This article points to a user profile corruption, but I recreating this user isn't an option. Are there any other ideas on cleaning this up? PLATFORM VERSION INFO Windows : 5.1.2600.196608 (Win32NT) Common Language Runtime : 2.0.50727.3082 System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)

How to get folder path for ClickOnce application

邮差的信 提交于 2019-11-27 10:15:27
I need to write a file in the same folder where a console ClickOnce .application (executable file) resides. The folder where it launches from. I tried using Application.StartupPath & Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location) but the path is pointing to a subfolder under c:\Documents & Settings . How do I get the path where the .application resides in? To find the folder location, you can just run the app, open the task manager (CTRL-SHIFT-ESC), select the app and right-click|Open file location. RobinDotNet path is pointing to a subfolder under c:\Documents & Settings That

Clear the .NET-downloaded application cache without Mage?

喜欢而已 提交于 2019-11-27 09:20:23
问题 I have a .NET application that I distribute using ClickOnce and I make available online only. How do I clear the download cache from a users' machine that doesn't have Visual Studio installed? 回答1: Visual Studio isn't needed, just Mage. It comes with the Windows SDK for people that haven't gotten it via Visual Studio or the Framework SDK. Another option would be to write code to clear the cache. Or you could have them delete the folder ClickOnce files are installed in ( C:\Users\[username]

Custom icon for ClickOnce application in 'Add or Remove Programs'

好久不见. 提交于 2019-11-27 09:04:30
A ClickOnce application created using Mage is not showing the icon that was specified in for the Mage command-line parameter in control panel Add or Remove Programs . I read some blogs, like: Application icon is not displayed in Add/Remove Programs dialog Missing Icon in Add/Remove Programs for ClickOnce Application How can I achieve this without editing registry keys? Is it possible? There's no way to do this without editing the registry, but you can do it programmatically. You have to be sure the icon is included in the deployment. We set our assembly description to the same string as our

ClickOnce Deployment Errors

妖精的绣舞 提交于 2019-11-27 08:17:12
问题 I am trying to deploy a ClickOnce app. It had worked previously when the server was just sitting with .Net 2.0 installed (no SP). Recently the server had 3.5SP1 installed on it and now ClickOnce is failing with the error: Value does not fall within the expected range inside System.Deployment . Here is the information posted on the MSDN forums (answers there are generally hit or miss for me) with the call stack: It was in VS 2005 w/SP1 and I tried changing the path I publish to, changing the