Dotnetpanel Forums

Hi guys,

I want to write my own client update wizard/manager and not use clickonce.  Can you point me in a direction to find documentation about this?  I take it you did this in dot net as a WinForm?  That would be great!

I found this article: http://www.codeproject.com/csharp/vanillaupdaterblock.asp

This seems like what I need but not in the same context of how you at DNP use updating, that is what I want to achieve

DNP Configuration Studio uses its own proprietary update algorithm.

Why the current DNP CS does not suite your need?

Feodor,

I think you've got me wrong, the updater for DNP components is very good; nice job!  I am looking to create an update application for my own WinForm application (nothing to do with DNP) and I simply like the way you have created your update application; I was looking for some links to tutorials regarding how I might do this.

Prior to running my own business I developed in house software and never had to write an updater application, ClickOnce was the only tool I used if I did as it was all on the same network and quick and simple for what I was trying to achieve.  I really wanted to explore writing an update application like the way you have for DNP; can you help point me in the right direction for this?

Hi Matt,

Do you need self-updated WinForm application like Reflector or separate updater like Configuration Studio?   

I wanted to write a self updating app with the option to be switched on or off but also a seperate app like Configuration Studio because I want to use it for other things like purchasing additional components for the base app as well as updating manually.

I'm guessing there is some sort of class from the dot net framework which checks a remote source for assembly versions on the remote application and compares them to the current one installed?

Anyway, if you have links to this sort of thing that would be great.

The general idea is as follows: CS stores all required info about installed components in its own configuration file. When you click "Check for update", CS sends installed version to the main configuration server via XML web service and asks whether a new version is available. If yes, CS downloads new version and replaces required files with new ones. If required, it executes SQL script against specified database. It's very simple, isn't :)? 

Yes, the concept is simple!  and an efficient way of doing things too.  What goes on around that is obviously more in depth, i.e. backing up data etc but the updating process is much easier than I expected.  I guess this is how you use your licence evalulation too as this is something I will have to cover.