clickonce

We have an app which I've coded up and for ages now I've pushed updates to it through ClickOnce. The app sits on our main file server. But every time I push out an update I get asked what I've changed! Is there any way to provide a personalised description of an update with ClickOnce which would be user-friendly? For example, when the user launches their application, ClickOnce asks "A new version is available. Would you like to update?", below which I could have a description of what I've updated? Or is this impossible with ClickOnce? Here's how I do it. I call this method in my startup code,

I am using clickonce for a windows forms application. I have to deploy some resource assemblies. These assemblies are in a folder in my project (not as a reference). They are marked BuildAction = content and CopyToOutputDir = Copy If Newer. With this configuration I'm getting the warning MSB3178: Assembly '' is incorrectly specified as a file. When I set the BuildAction to none, the warnings disappear, but the assemblies that must deploy not appear in ClickOnce Application Files. I would like to add these assemblies (there are many) in the publication of clickonce without this warning and

Is it possible to deploy a native Delphi application with ClickOnce without a stub C# exe that would be used to launch the Delphi application? The same question applies to VB6, C++ and other native Windows applications. Personally, I build my own mechanism to kick off self update process when my application timestamp is out of sync with the server. Not too difficult, but it's not a simple task. By the way, for Delphi you can use some thirdparty help: http://www.tmssoftware.com/site/wupdate.asp UPDATED: For my implementation: MyApp.EXE will run in 3 different modes MyApp.EXE without any

I've had a ClickOnce app in use for a few months now, but recently started getting an error on my deployment of the latest version. With this latest version I've added a reference to a DLL that I hadn't used before ( FTD2XX_NET.dll if it's relevant), and suspect that this is related to the issue but I cannot figure out how to fix it. The actual project being deployed references another library project, which is what references the DLL (it references other DLL's but that has worked for months and they haven't changed). Following these threads I've tried deleting my "Local Settings/Apps" folder

I'm going to set up this question and answer it myself, so that others could search and find the correct answer easierly. I had to google for hours and compile the end result from multiple sources... So the question is - how to enable Per-Monitor v2 DPI awareness in a ClickOnce scenario (WPF, c# specifically)? Per-Monitor v2 was added in Win 10 Creators Update (1703). ClickOnce notoriously does not support DPI awareness declared in an app.manifest file, like this . First of all, anyone who want's to cry out - simply target .NET 4.6.2, per monitor DPI awareness is enabled by default - that is

I have a C# application which is run through a database, and it is being used by different people in different locations. The easiest and best way to update my application every time there is a change was to create a ClickOnce application and publish it to a server. My problem is that the only server I can have is an FTP server and the problem here is that ClickOnce doesn't support to get updates from the FTP server. It supports updating to a file share or web hosting. So I need some opinion on how should I update my application. Is there a chance to access the FTP server through HTTP? For