Email Password Remember me?  Lost your password?

• Download source files - 243.9 KB

Introduction

Automatically deploying your applications/resources/related files is a common and recurring problem that every developer making software for a large audience has to face!
WebUpdate offers a real easy and fast way to add a self-update ability to your application!

• Update any kind of file based on date check
• Each file can be updated individually (no need to redownload a full version if only one little file has changed)
• No need to make a configuration file and specify manually each file that requires an update
• All communications between the client and the Web service (the webupdate server part) are compressed to gain up to 60 % of bandwidth and update time!
• Threaded
• Reconstructs files and directories that have been deleted by the user
• Easy to add to any project (less than 5 minutes!!!)
• Easy to add a new update (put or overwrite files to be added/updated in the update folder on the server)
• Automatically starts at startup or shutdown of your application
• Ability to update the updater software!

Background

Before starting the development of webupdate (2004), I searched if someone had made something similar and I discovered Microsoft's application blocks : "Updater Application Block" which does the same thing but has some limitations:

• The block relies on absolute path links being provided in the configuration file. This reliance causes big problems, because you can't always guarantee that users will install your application to a specific location.
• When you want to add a new file to be updated, you have to modify a manifest file to set the file path for each file!
• You have to play with a public/private RSA key. :(
• A version is a set of files. So, if you want to update just one file you have to prepare a new update folder with a new manifest!
• Every time the Updater downloads a new version of your application to the client, it creates a new folder to contain the new version; unfortunately, it leaves the folder(s) for the outdated version of your application and all its files intact. That's untidy. It leaves open the possibility for users to run an older version, and bloats the disk space requirements for your application.

Hopefully those limitations can be removed by extending the updater block with the interfaces IValidator, IPostProcessor and IDownloader but that is not the subject of this article.;)

The Update Process

A user starts your application, your application launches WebUpdate.exe.
WebUpdate asks the update server if WebUpdateClient.exe was updated and updates it if necessary. Webupdate.exe starts webupdateclient.exe which is the real updater. WebUpdateClient asks the server (a Web service installed on a Web server) for all file info about an appname (paths, sizes, last modifications) and compares the results to the local folder. Finally WebUpdateClient.exe asks for the required files. The server sends in response the required files through a compressed soap message. All updated files are updated or added to the application folder.

Using the Code

Given below is the code to add to your existing application Load method:

System.Diagnostics.ProcessStartInfo psi = new System.Diagnostics.ProcessStartInfo();
psi.Arguments = "check";
psi.FileName = Application.StartupPath + "\\WebUpdate.exe";
psi.WorkingDirectory = Application.StartupPath + "\\";
psi.UseShellExecute = true;

System.Diagnostics.Process.Start( psi );

How To Install the Demo?

1. Unzip webupdate_src.zip
2. Create a virtual Web site for the folder WebUpdateWS
3. Place some files to be updated or added on all clients computer in the folder WebUpdateWS\Updates\YOUR_APP_NAME_HERE\
4. Edit the webupdateclient\bin\Debug\WebUpdate.ini file and set the line "Version=" to "Version=YOUR_APP_NAME_HERE"
5. You can directly run a webupdate by launching webupdateclient\bin\Debug\WebUpdate.exe

Of course in a real application, you just need to xcopy all the contents of webupdateclient\bin\Debug\ near your main EXE and modify WebUpdate.exe.config and WebUpdateClient.exe.config to set the real Internet webupdate server HTTP address.

About the Compression

I used the library SharpZipLib and the excellent SoapExtender CompressionExtension from Saurabh Nandu.

Feel free to ask me any questions.
Joseph Benguira joseph@z51.biz

You must Sign In to use this message board.

Per page 102550

FirstPrevNext

Simple and effective, thanks! Spaceman1 3:06 23 Sep '09   This is exactly the level of solution I was looking for. Thanks. Sign In·View Thread·PermaLink {"Response is not well-formed XML."} Joseph Urso 9:02 5 Mar '09   Hello I receive {"Response is not well-formed XML."} when executing: object[] results = this.Invoke("GetAllUpdateInfosCompressed", new object[] { version}); I see that you received this report quite a while ago but there is no public response posted. Can you give a hint about how to fix this. Thank You Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} jocool2550 10:28 5 Mar '09   have you checked this message : http://www.codeproject.com/script/Forums/View.aspx?fid=278224&msg=1455457 Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} Joseph Urso 10:48 5 Mar '09   Hi, Yes I saw that and had added the [CompressionExtension] The code looks like this: [CompressionExtension] [System.Web.Services.Protocols.SoapDocumentMethodAttribute ("http://tempuri.org/GetAllUpdateInfosCompressed", RequestNamespace = "http://tempuri.org/", ResponseNamespace = "http://tempuri.org/", Use = System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle = System.Web.Services.Protocols.SoapParameterStyle.Wrapped)] public object[] GetAllUpdateInfosCompressed(string version) { object[] results = this.Invoke("GetAllUpdateInfosCompressed", new object[] { version}); return ((object[])(results[0])); } The exception looks like this: System.InvalidOperationException was unhandled Message="Response is not well-formed XML." Source="System.Web.Services" StackTrace: at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String MethodName, Object[] parameters) at WebUpdateClient.ws_update.Update.GetAllUpdateInfosCompressed(String version) in C:\WebUpdate\webupdateclient\Web References\ws_update\Reference.cs:line 51 at WebUpdateClient.Form1.button1_Click(Object sender, EventArgs e) in C:\WebUpdate\webupdateclient\Form1.cs:line 174 at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at system.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.Run(Form mainForm) at WebUpdateClient.Form1.Main() in C:\WebUpdate\webupdateclient\Form1.cs:line 158 at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args) at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args) at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} jocool2550 11:14 5 Mar '09   this is because you get compressed XML from the server and it's not correctly uncompressed on the client ... if you want you can call GetAllUpdateInfos instead of GetAllUpdateInfosCompressed to get ride of this problem Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} Joseph Urso 6:02 6 Mar '09   Thank You for your responses, But, the web service does not have a function defined as "GetAllUpdateInfos", have I downloaded a non current version? But, why would the compressed XML not uncompress correctly? I tried removing the compression by "//[CompressionExtension]" but I then get the error "Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'." This looks like a really great solution and I would really like to get it working. Thank You Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} jocool2550 6:04 6 Mar '09   if you juste want to use it, just dont try to recompile it it will work out of the box ... all the problems are caused by vs 2005 or 2008 wich break the reference file from vs2003 Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} Joseph Urso 7:43 9 Mar '09   I do need to support the app and I do need to compile it. I did make progress though.... I tried to do an “update web reference” for "ws_update" in the WebUpdateClient workspace and received an IIS metabase error. I tried to resolve that error with the fix at this link http://geekswithblogs.net/narent/archive/2007/03/23/109573.aspx by issuing the command line command “aspnet_regiis –i” as defined in that web page. After doing that, the “Response is not well formed-XML” exception encountered at "GetAllUpdateInfosCompressed()" was fixed and downloading of the files worked also. Of course, if you actually do the "update web reference", the generated Reference.cs file gets overwritten and you will have to add the compression modifications again. Joe Sign In·View Thread·PermaLink Re: {"Response is not well-formed XML."} jocool2550 7:56 9 Mar '09   thanks for publishing this solution Sign In·View Thread·PermaLink Administrator rights needed? BBiales 7:09 27 Feb '09   Hi, We have an application that is currently being updated with an updater developed around the Patterns and Practices Updater Block. We now find that updates are only successful, when updating the exe or dll files, when the logged on user has administrative rights . Can I assume your updater will run into the same issues? Do you have any suggestions? Should we be changing the security for our software folder to allow other users access to it? Thanks for any insight. I plan to try out your code and use it in the future to avoid all the overhead with the updater block's manifest creation process... Oh, and one other question - Do you think it would be difficult to make the update process a "two phase" process? Where we can start a download of updated files, but start the application right away. Then install those files the next time the user starts the application? Our app runs over a WAN connection, and updates may take quite some time to download, that is why I ask. Thanks for a great tool. Sign In·View Thread·PermaLink Re: Administrator rights needed? jocool2550 10:42 27 Feb '09   Hello, my updater doesn't need the user to have admin rights And unlike the updater application block, my updater detect updates on any files !! not only assemblies For your 2 phases process ... it's not possible because the way my updater work is by comparing local and remote files... a way to do it could be to first copy the full app folder then run the updater on the copy and run your app in the original folder, then at each launch rename the copy folder to the original folder name Sign In·View Thread·PermaLink Assembly does not allow partially trusted callers shawn32 7:47 15 Jan '09   Hello. I have used this service many times in the past and it has always worked great for me. However, in a recent implementation, I came across the following exception: Client found response content type of 'text/plain; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Security.SecurityException: That assembly does not allow partially trusted callers. at System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly asm, PermissionSet granted, PermissionSet refused, RuntimeMethodHandle rmh, SecurityAction action, Object demand, IPermission permThatFailed) at MasterCSharp.WebServices.CompressionExtension.Unzip(String stringToUnzip) at MasterCSharp.WebServices.CompressionExtension.UnzipSoap(Stream streamToUnzip) at MasterCSharp.WebServices.CompressionExtension.Unzip() at MasterCSharp.WebServices.CompressionExtension.ProcessMessage(SoapMessage message) at System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException) at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest() The action that failed was: LinkDemand The assembly or AppDomain that failed was: CompressionExtension, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null The Zone of the assembly that failed was: MyComputer The Url of the assembly that failed was: file:///D:/Hosting/3553549/html/updates/bin/CompressionExtension.DLL --- End of inner exception stack trace --- --. Has anybody seen this or know why this might be occurring? Thanks! Sign In·View Thread·PermaLink Re: Assembly does not allow partially trusted callers jocool2550 8:29 15 Jan '09   You are certainly deploying your client through clickonce, you have to set full trust to your clickonce app Sign In·View Thread·PermaLink Re: Assembly does not allow partially trusted callers shawn32 9:01 15 Jan '09   You are correct. I have just confirmed that my hosting provider (GoDaddy) no long supports Full Trust for their Shared hosting accounts. They will however enable Full Trust if I purchase a virtual server account. As that is not an option due to the tremendous difference in cost I will most likely develop an FTP solution instead. Thanks. -Shawn Sign In·View Thread·PermaLink using the client on a web site gedw99 10:29 22 Oct '08   Hey, Can i use this on an Asp.net web site to allow itself to call another server to get an update ? The aspect of updating itself is why i ask this question. Sign In·View Thread·PermaLink How to implement? DuBro 7:08 30 Mar '08   Ok sorry if this is a stupid question.. but how am I supposed to implement this into my application? I can't run the WebUpdateClient.exe app from my app's load event since it wont be able to overwrite the exe currently running. Am I then supposed to run the WebUpdateClient.exe first and then on its completion run my application? Sorry, just a bit confused here. Thanks Sign In·View Thread·PermaLink 2.00/5 Re: How to implement? jocool2550 3:12 1 Apr '08   Your user should start webupdate.exe, this will update webupdateClient.Exe and start your application update then you can modify webupdateClient.exe to start your application.exe at the end of the update Sign In·View Thread·PermaLink 1.00/5 MD5 Hash instead of file time Jacques Doubell 22:25 30 Jan '08   Thanks for providing WebUpdate, its a simple and effective solution for my updating needs. I made a change to include the file's md5 hash as a field in the UpdateInfos class and I use that now instead of the file time to check if a file needs to be updated. The reason for this was that when uploading a new version to the website folder the ftp client affected all the files times so all the files would be downloaded instead of only the ones that had really changed. Sign In·View Thread·PermaLink Re: MD5 Hash instead of file time jocool2550 10:54 31 Jan '08   MD5 is a Great idea instead of timestamp Sign In·View Thread·PermaLink 2.00/5 Yet another request for posting the VS2005 Version dirk_kaiser 0:37 6 Jul '07   Joe - I'm very sure that I am correctly doing the code changes that you have previously posted about what to modify after VS2005 does it's upgrade; but I'm still having problems. I've tried from scratch 3 times now with no luck. So, any chance you could post your VS2005 version as clearly there is something else going on? Thanks, Dirk Sign In·View Thread·PermaLink 2.00/5 Database SQL Updates ? Hantoush 16:26 18 Jun '07   What about updating the user database - SQl ? Smetimes we have to update the SQL ? Any idea about the best way to do it ?? thanks again Hantoush Sign In·View Thread·PermaLink 1.00/5 Re: Database SQL Updates ? jocool2550 22:23 18 Jun '07   Your main EXE should reconstruct sql tables/columns or convert data to new format at each start Sign In·View Thread·PermaLink 4.00/5 Does it work on webserver with PHP/MYSQL? Hantoush 16:21 18 Jun '07   Hi , My web server supports Linux with PHP/Mysql .. Can I use WebUpdate ? or I have to upgrade to Windows ASP .NET web server ? thanks Hantoush Sign In·View Thread·PermaLink Re: Does it work on webserver with PHP/MYSQL? jocool2550 22:21 18 Jun '07   only work on an asp.net server Sign In·View Thread·PermaLink "Proxy Authentication Required" fhei 2:11 12 Jun '07   Hi, nice work! But it´s not working here. I´m sitting behind a Proxy Server. Each time i start the client i´m thrown out with the exception "...407: Proxy Authentication Required." Any idea where to put my login/pw for my WWW-Proxy and why i´m asked for this ? The HTTP server is running local. Thanks in advance ! Frank Sign In·View Thread·PermaLink

Last Visit: 4:26 22 Nov '09     Last Update: 4:26 22 Nov '09 12345 Next »