Geek Answers Handbook

How do you handle software updates that you are developing?

I am developing C # desktop software for mid-sized companies, and I am looking for a good strategy to deploy software updates for my clients.

  • How do you deal with this?
  • Are you using the windows installer?
  • Is this the best choice to develop my custom updater? Have you already developed similar things? Do you have best practices for sharing?
  • Are you using any other library or existing software?

thanks

+4
source share
4 answers

Or you can use a third-party component Update component

Here is the documentation .

+2
source

I am developing several open source applications, some of which are being updated, and some are just proof of concept.

When it came to deciding the best way to update the software, I decided to use the ClickOnce route, which is present in Visual Studio, and not only automatically installs any necessary .Net Framework files, but it can also download updates from the specified web server when the application starts. as well as at the time of my choice.

I believe this is the easiest way to release updates for my applications, there may be more complex methods, but given my open source applications, there are no corporate requirements or deadlines that I think ClickOnce is more suitable for this. goals.

Note. I write my applications in C # and either .Net 3.5 or .Net 4.

Link: Selecting a ClickOnce Update Method

+3
source

Windows Installer with WIX has become extremely simple and competent for updates, however, if you are doing something complicated in your installer, you can really think about creating automatic updates in your applications. As long as you can depend on how your clients run .net, it’s pretty easy to make applications that do this for you.

+2
source

If you plan to automate the update process, I would suggest that you want to do this via the Internet or any other corporate network.

So, in this case, it would be best to develop a client-side server installer, where new files (or any package containing such files) and a script installation (which can be anything from a batch file to a custom written installer with your own rules for installation steps) will be hosted on the server, and you will have a thin client running on client computers that simply downloads packages and scripts and starts to execute them on the client.

Now, what part of the “setup” you want to do in the installer engine depends on the flexibility you need.

+1
source

More articles:


All Articles