The Kinetic Jump site navigation header requires JavaScript to be enabled and the latest version of the Macromedia Flash Player. If you are you using a browser with JavaScript disabled please enable it now. Otherwise, please update your version of the free Flash Player by downloading here.

Welcome Guest Search | Active Topics | Log In | Register

Updating Framework 1.1 Applications Options
Previous Topic · Next Topic
brianh
#1 Posted : Wednesday, August 15, 2007 10:28:54 AM
Rank: Administration
Groups: Member, Administration

Joined: 5/24/2007
Posts: 362
Location: Minnesota
I fielded an inquiry on how to use AppLife Update with a Framework 1.1 application. Since AppLife Update requires the 2.0 framework, it must be present to function. But if your willing to place the 2.0 framework with your application, here is an implementation that you could use.

Framework 1.1 Updater overview

Unzip the attached zip file. It includes the following:

AppLifeUpdater - This is a .Net 2.0 VS 2005 application that initiates an update process on behalf of the configured 1.1 application.

Framework11DemoApp - This is a .Net 1.1 VS 2003 application that is updated by the AppLifeUpdater.

Framework11DemoApp.aup - This is the AppLife project file for the application.

To set up and execute this Example:

1. Open the AppLifeUpdater solution in VS 2005
2. Set the update location on line 46 of program.cs to a new location on your network.
3. Rebuild AppLifeUpdater
4. Move the newly built AppLifeUpdater.exe to the bin folder of the Framework11DemoApp
5. Open the Framework11DemoApp.aup file in Make Update
6. Modify the publish location to match the location set in step 2
7. Change the path of the Framework11Demo.exe within the Add & replace file action to the zip location/v2 directory. This update replaces the Framework11DemoApp.exe.
8. Publish an update.
9. From the Framework11DemoApp bin folder, run the Framework11DemoApp. Click the check for updates button. You should be able to check for updates, accept and apply the update. Framework11DemoApp v1.0 will be replaced with v2.0 and relaunched.


Please review the code comments of the AppLifeUpdater solution for details on how this works. The general operation is like this.

The AppLifeUpdater.exe hosts the AppLifeUpdate Controller and is dependent on the 2.0 framework. When the Framework11DemoApp wants to check for and apply updates, it launches the AppLifeUpdater.exe and passes a few parameters on the commandline. The AppLifeUpdater.exe checks for and downloads any available updates. Before applying the update, the AppLifeUpdater will attempt to close any instances of the Framework11DemoApp. The Framework11DemoApp is replaced during the update and the AppLifeUpdater relaunches the Framework11DemoApp.
Brian Haas
Kinetic Jump Software
Back to top
WWW  Report Abusive | Report SPAM
brianh
#2 Posted : Tuesday, January 20, 2009 9:41:52 AM
Rank: Administration
Groups: Member, Administration

Joined: 5/24/2007
Posts: 362
Location: Minnesota

Here is an updater example that takes advantage of new features of the Update Controller that greatly simplifies updating Framework 1.1 applications (native C, and VB6 apps as well). 

 

The .Net Framework 2.0 is still required on the client system.

 

NOTES:

 

The stand alone executable in this example can be configured to update any application (native, vb6, framework 1.1).  The .Net Framework 2.0 must be present on the client system.  The updater can be launched separate from the application being updated as well as from code within the application.  Follow the steps outlined below to configure the updater application.

 

1.       Place the following files into the application directory (or a sub directory) of the application to be made updateable.

 AppLifeUpdater.exe
Kjs.AppLIfe.Update.Controller.dll
updaterConfiguration.xml

2.       Create a new AppLife Update Project (aup) file.  Create a network update folder for your application to retrieve updates from.

3.       Open the updaterConfigration.xml file that was placed into the application directory in step 1 for edit.

4.       From the AppLife Update project properties dialog, copy the application ID to the configuration file.

5.       Edit the host process name in the configuration file.  This is the usually the name of the application executable without the extension.

6.       Edit the host assembly location.  Set this relative to the location of the updater exe. (eg ..\host.exe if placed in a sub folder)

7.       Edit the update location to match the location created in step 2.

8.       Replace the inner value of the PublicKey file element with the public key of the aup project file. This can be viewed by selecting to View Public Key from the Tools menu within the AppLife Update client application. You can copy this from the output window to the configuration file.

9.       Save the configuration file.

 

From within the update project, the host assembly location configured in step 6 above maps to the Application Directory.  So to create an update that will update your application, add file actions that include the new files and targets placing them in the Application Directory.

 

Executing the updater will check the configured update location for update, download, and apply them.

File Attachment(s):
AppLifeUpdater.zip (22kb) downloaded 17 time(s).
Brian Haas
Kinetic Jump Software
Back to top
WWW  Report Abusive | Report SPAM | Edit by user: Tuesday, January 20, 2009 9:44 AM | Reason: Not specified
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2009, Yet Another Forum.NET
2010 © Kinetic Jump Software, LLC \ Privacy Policy \ Blog
\ Home \ Products \ Solution Lab \ Downloads \ Support \ Company \ Store