Enhancing my installer

[NewsArchive]

Hi
Until now I have made normal installations with SB7 : Go to my homepage, run
the installer. I am working on a project now where I would have to spend 1/2
hour guiding users with no pc experience. So it is time to say Hello to
wupdate and the world this opens.
I have used the Coolapp example and have it running now. I have some doubt
about the directory structure on the server: Coolapp is for the initial
installer = Version 1.00, and Web is for version 2.00 Now, what about
version 3.00 and 4.00 Do I place them in a new directory each ( /web
/web3oo /web400 ) or do I just always put the latest version in /web ?

I am also looking at the Serial-number-key and Subscription-key thing. Here
is what I would like to know if I can do:
Today I use Armadillo. Lock the program to a company name with no time
limit.
I would like to make a Subscription feature like the one in SB7, but with a
different behavior when the subscription ends: The program must not just
keep on working, it has to put on some limitations. Go from Pro to Free,
limit record number or something else. Is this possible in SB7 ? Would it
replace Armadillo or work together with Armadillo ?

--
Best regards
Viggo Poulsen
www.vipilon.dk

[NewsArchive]

Hi Viggo,

> Until now I have made normal installations with SB7 : Go to my homepage,
> run the installer. I am working on a project now where I would have to
> spend 1/2 hour guiding users with no pc experience. So it is time to say
> Hello to wupdate and the world this opens.
> I have used the Coolapp example and have it running now. I have some
> doubt about the directory structure on the server: Coolapp is for the
> initial installer = Version 1.00, and Web is for version 2.00 Now, what
> about version 3.00 and 4.00 Do I place them in a new directory each
> ( /web /web3oo /web400 ) or do I just always put the latest version in
> /web ?

Unfortunately, there is no general answer to that question. It always
depends on your own "deployment strategy".

If your deployment strategy allows to "web update" from Version 1.0 to
Version 4.0, then sure, no problem. You can do this with SetupBuilder. And
if your deployment strategy allows to handle web updates for a specific
version only, then you can also handle this. But only you (the developer of
the application) can decide what to do.

As an example, see web updates for Windows or SetupBuilder. The web update
process for both products does not allow to "live-update" from Windows XP to
Windows 7 or from SetupBuilder 6 to SetupBuilder 7 -- that's a deployment
strategy decision. From the technical point-of-view, it would be possible
to live-update from SetupBuilder V6 to V7. But we don't do this.

> I am also looking at the Serial-number-key and Subscription-key thing.
> Here is what I would like to know if I can do:
> Today I use Armadillo. Lock the program to a company name with no time
> limit.
> I would like to make a Subscription feature like the one in SB7, but with
> a different behavior when the subscription ends: The program must not just
> keep on working, it has to put on some limitations. Go from Pro to Free,
> limit record number or something else. Is this possible in SB7 ? Would it
> replace Armadillo or work together with Armadillo ?

Armadillo works at the application level. It's a software (license)
protection system.

SetupBuilder makes use of our setupPROTECT technology to protect your setups
(installs and updates). For example, if a subscription key expired, then
it's not possible to install/update a version that was released after the
expiration date. But even with an expired subscription key, you can still
use (install) the version that you were entitled to use.

Does this help?

Friedrich

[NewsArchive]

Hi Friedrich

Yes, I understand that it can be done in many different ways. I only have 1
program version ( which is always allowed for everyone to install ). It may
be V1.00 V2.35 etc. but customers (who have paid an annual amount) who
started with one version are free to upgrade to the newest version whenever
wanted.
In this case I suppose that if I have one directory for the initial install
and another for the newest install, it should work ?

I think that JP's description is very close to what I need, so I'll dig into
that.
Thank you for your answers.

Viggo Poulsen.

[NewsArchive]

Hi Viggo,

> Yes, I understand that it can be done in many different ways. I only
> have 1 program version ( which is always allowed for everyone to
> install ). It may be V1.00 V2.35 etc. but customers (who have paid an
> annual amount) who started with one version are free to upgrade to the
> newest version whenever wanted.
> In this case I suppose that if I have one directory for the initial
> install and another for the newest install, it should work ?

In this case (if the "new" version always replaces the "old" one and the
Product GUID does not change), you can use the same web install project and
let web update bring the installed version to the latest build. The web
update technology will then download/install only what is required for the
specific machines.

Friedrich

[NewsArchive]

Hi Friedrich

Perfect, just what I need.

Viggo Poulsen

[NewsArchive]

Viggo,

DMC for example uses ONE folder for all webupdates -> this means that
if the suer has vX and current update is for vX+5 then he can
_download_ it

Dowload does not mean install

This is where MP subscription enters in play

If the sub is current then he can install it

If the sub is ellapsed then he cannot install it

I use inbuilt functions in SB to check the dates

I use SB7 to STORE the dates in an HKLM level key which only elevated
apps can write to

In DMC I READ those dates and COPY them to HKCU as there I can write
not being elevated

Of course I added code in my app and in SB to double check a user did
not tamper with the dates I wrote in reg ;)

Regarding levels in your app - this _you_ need to code

What you could do is simply read the exp date from reg and if expired
then set a flag (Free) to True and if current the flag becomes (Pro)

Then in your app _you_ add limits - chose the ones you prefer - I opted
simply for a single procedure to add and called before each 'task' and
depending on result received I limit to X Nb records for example.....

No use adding templates to do all this as it is very easy and
straightforward

--
Merci
Cordialement - Best regards
__________________________________________________ _____

For those who do not understand ... : "Qui bene amat bene castigat."
__________________________________________________ _____

DMC - Data Management Center : a tool to let you Migrate Import Export
Transfer your Data
www.dmc-fr.com/database_migration.html Certified by Microsoft : "Works
with Vista" & "Works with Windows Server 2008"

[NewsArchive]

Hi JP

Thank you for your explanation. This seems to be just what I needed to get
me on the right track.

Best regards
Viggo Poulsen.