- Why can't I find the installation directory? (ClickOnce doesn't use the standard C:/Program Files/ location, it stores program files in C:/Users/<your username>/AppData/Local/Apps/2.0 for security reasons.)
- Why does the installer need a network connection? (ClickOnce downloads the required setup files from the internet.)
The lack of a standard Program Files/.exe deployment also makes it difficult to map filetype associations, which is also a frequent complaint.
I'll likely be going with non-ClickOnce deployments for the future. ClickOnce is great for deploying production software at work, but for a consumer audience, it isn't quite perfect.
Considering that Paul has been working on it and yet choose to go with ClickOnce, I am guessing it's not ready for prime time but it might be worth looking into anyway.
NSync isn't finished yet - ClickOnce is 95% of what we want but has some pretty damning flaws (tells people randomly that an app is "Unknown Publisher", certs expire after one year and now people have to uninstall/reinstall, proxy server problems, etc).
NSync is my ongoing (not finished yet!) project to recreate ClickOnce
BTW is there a way to submit tickets other than email for GitHub for Windows? Maybe a GitHub repo? Would make it rather easy to submit and track issues while also limiting the number of duplicates.
NSync has a somewhat novel mechanism of delivering updates (via repurposed NuGet packages) that would be difficult to shoehorn into NAppUpdate or other frameworks
Yes I've been keeping a close eye on this project. Based off the readme, it sounds exactly like what I'm looking for. You make a good point though, as it was authored by the same user but ClickOnce was chosen instead.
I fucking hate ClickOnce. The crappy downloader fails all the time. Not all places have a good QoS connection like North America. HTTP download can be restarted and resumed at anytime.
Yes and it's actually really easy to do, it's built right into Visual Studio. The downsides are that you can't really do anything with it after you've set them (like at application runtime), the associations don't always work for some reason, and if the associations get changed by other applications you can't reset them unless the user re-runs the installer.
- Why can't I find the installation directory? (ClickOnce doesn't use the standard C:/Program Files/ location, it stores program files in C:/Users/<your username>/AppData/Local/Apps/2.0 for security reasons.)
- Why does the installer need a network connection? (ClickOnce downloads the required setup files from the internet.)
The lack of a standard Program Files/.exe deployment also makes it difficult to map filetype associations, which is also a frequent complaint.
I'll likely be going with non-ClickOnce deployments for the future. ClickOnce is great for deploying production software at work, but for a consumer audience, it isn't quite perfect.
(Personally, I really like ClickOnce.)