Test folder for webupdate

[NewsArchive]

Hi Friedrich,

Before I publish a webupdate I test it, but this is a bit of a
problematic process.

If I upload to the "public" folder then anyone could get to the
webupdate while I'm testing it.

The only other option that I can see is to save the sb6 project to a
test project, change the Host directory in the install and also in the
registry on the test computer so it can find the correct folder, and
then try it.

Neither option is good an in both options things can go wrong. Do you
(or anyone else) have any word of advise on how to best do this? Am I
overlooking something in the web deployment setup?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

>The only other option that I can see is to save the sb6 project to a
>test project, change the Host directory in the install and also in the
>registry on the test computer so it can find the correct folder, and
>then try it.

Well, scratch that<g> That didn't work at all - it seemed to get
mixed up in which folder to look in as it would report that the file
downloaed didn't match the exepected file from the server.

Fortunately, testing the webupdate this time didn't take long<g>

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Well, scratch that<g> That didn't work at all - it seemed to get
> mixed up in which folder to look in as it would report that the file
> downloaed didn't match the exepected file from the server.
>
> Fortunately, testing the webupdate this time didn't take long<g>

:)

What we do is the following:

The web updates are always uniquely named, for example "sb6_2266_dev.exe"
for Build 2266. The Server manifest file for SetupBuilder is named
"sb60_dev.ini"

Okay, we compile the web update project. But before we upload the files to
the web server, we rename the server manifest file "sb60_dev.ini" to
"sb60_devX.ini". Then we upload all files.

Now I can test the web update. I install the previous version and change
the HOST_INI value data in the registry
HKEY_LOCAL_MACHINE\Software\Lindersoft\WebUpdate\A pps\<YOUR_GUID> from
"sb60_dev.ini" to "sb60_devX.ini" (see above).

That's it <g>. I can test the "new" web update now and the real "old" web
update is still available.

If web update works fine, I delete the real "sb60_dev.ini" on the web server
and rename "sb60_devX.ini" back to "sb60_dev.ini". This takes 0.0001
seconds <g> and the new web update is ready to go. A few minutes later, I
remove all old web update files (e.g. sb6_2243_dev.exe, sb6_2243_dev.00001,
etc.)

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

>The web updates are always uniquely named, for example "sb6_2266_dev.exe"
>for Build 2266. The Server manifest file for SetupBuilder is named
>"sb60_dev.ini"

Aha, that's how you do it. Is it enough just to change the output exe
name and the rest of the files will follow?

>Now I can test the web update. I install the previous version and change
>the HOST_INI value data in the registry
>HKEY_LOCAL_MACHINE\Software\Lindersoft\WebUpdate\A pps\<YOUR_GUID> from
>"sb60_dev.ini" to "sb60_devX.ini" (see above).

Cool!

I tried to upload to a different folder and change things to deal with
that, but it appeared that the install still tried to pull the files
from the original folder which caused mismatch.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

> The web updates are always uniquely named, for example "sb6_2266_dev.exe"
> for Build 2266. The Server manifest file for SetupBuilder is named
> "sb60_dev.ini"

I just wanted to let you know that I have tried this and it worked great. I
set a SB variable in my Build Automator script for the Web update and use
that variable - which contains the build number - as part of the destination
exe name in the SB script. Worked like a charm:)

--
Arnór Baldvinsson - Icetips Creative, Inc.
www.icetips.com - www.buildautomator.com

Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>> The web updates are always uniquely named, for example "sb6_2266_dev.exe"
>> for Build 2266. The Server manifest file for SetupBuilder is named
>> "sb60_dev.ini"
>
> I just wanted to let you know that I have tried this and it worked great.
> I set a SB variable in my Build Automator script for the Web update and
> use that variable - which contains the build number - as part of the
> destination exe name in the SB script. Worked like a charm:)

Perfect!!! :) Thanks for the info!

Friedrich