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

Update History Options
Previous Topic · Next Topic
tndlovu
#1 Posted : Wednesday, January 18, 2012 6:06:34 AM
Rank: Member
Groups: Member

Joined: 1/18/2012
Posts: 8
Location: South Africa

Hi everyone "that will read this".

I have this scenario where I use applife to update two applications, say Application1 and Application2. The problem that I have is, the Update history displays Updates of both applications, regardless of the the application that has been selected. I would like to make it known that I was not responsible for the writting the Update Manager, however, according to the documentation, the Update history uses the log files that gets generated with every update that gets applied. I did notice that there is nothing on the file name that could be used to identify the application to which a log file belongs.

This makes it hard for an average user (client) to locate a specific log that belongs to a particular application. Is there any development around this?
Back to top
WWW  Report Abusive | Report SPAM
brianh
#2 Posted : Sunday, January 22, 2012 7:06:47 AM
Rank: Administration
Groups: Member, Administration

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

Hello,

 

The Update History logs are identified by Application ID. Each application that is updated should have a unique guid id that is assigned to the update controller.

 

If your solution is using the methods of the Update Controller that retrieve update history, such as the GetUpdateHistory method, then both of your applications are probably assigned the same application id.

 

Changing the application id of an application has a complication.  An Update Location can only hold updates for one application id.  Therefore, I recommend that when you change the application id, you also create a new update location (folder) and publish your next update there (after changing the application id of the Make Update project file to match).

Brian Haas
Kinetic Jump Software
Back to top
WWW  Report Abusive | Report SPAM
tndlovu
#3 Posted : Friday, April 13, 2012 6:33:57 AM
Rank: Member
Groups: Member

Joined: 1/18/2012
Posts: 8
Location: South Africa
brianh wrote:

Hello,

 

The Update History logs are identified by Application ID. Each application that is updated should have a unique guid id that is assigned to the update controller.

 

If your solution is using the methods of the Update Controller that retrieve update history, such as the GetUpdateHistory method, then both of your applications are probably assigned the same application id.

 

Changing the application id of an application has a complication.  An Update Location can only hold updates for one application id.  Therefore, I recommend that when you change the application id, you also create a new update location (folder) and publish your next update there (after changing the application id of the Make Update project file to match).

Thankx Brian 
Back to top
WWW  Report Abusive | Report SPAM
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