Web Update

[Steve Stockstill]

Is it possible to use WebUpdate for applications that are iistalled in the same client directory? It looks like the registry key (AppPaths) is based on the instal path and the wupdate.exe name.

Otherwise maybe I could use a different EXE names for wupdate.exe ? If so, what would be the best way to handle that?

Thanks,
Steve

[linder]

Steve,

The system is based on a unique GUID (see General Information properties). So different products (in the same folder) should work fine (with the same wupdate.exe).

Does this help?

[Steve Stockstill]

Wow, that was a fast answer!

I was just reviewing the implementation in wupdate.sb5 and it looks like it retrieves the GUID based on the AppPath. How does wupdate.exe know which instllation to update? Can I pass a parameter to force the GUID? Or am I misunderstanding something? Which could entirely be he case

Thanks,
Steve

[linder]

My answer was fast, but I fear it was not correct <g> I have to check this and get back to you.

I'll give you a correct answer tomorrow morning...

A very Merry Christmas!

[Steve Stockstill]

Not a problem
Merry Christmas to you as well!

Great product by the way!

Steve

[Steve Stockstill]

>> I'll give you a correct answer tomorrow morning...


I can wait, no hurry especially on Christmas

Steve

[linder]

Hi Steve,



My answer was "half correct". By default, one wupdate.exe can only live update one application in one specific folder. To update the second application, please do is the following:

1. From within the \Lib folder, copy wupdate.exe into wupdate_product2.exe

2. You have the following in your script:

Include WebUpdate Client "[SB5_LIB]\wupdate.exe"

Please change this to:

Include WebUpdate Client "[SB5_LIB]\wupdate_product2.exe"

BTW, you can use the above method for product3, product4, etc.

Does this help?

Thanks,

[Steve Stockstill]

Thanks for your help, that should do it. Thanks, Steve

[Steve Stockstill]

OK, we're getting closer. The problem is the regkey is still pointing to WUPDATE.EXE and not the newly named WUPDATE_PROG1.EXE, etc. When WUPDATE_PROG1.EXE executes it cannot find it's regstry entry and fails. If I manually create the registry entry using the WUPDATE_PRG1.EXE value entry it works fine.

[linder]

You are right. This will be changed in the next build. Thank you for bringing this to my attention.

Friedrich