On Windows, and am using the auto-update architecture, i.e. a compiled
auto-loader app that pulls non-compiled main stack updates from the network. I
have two questions that I would like advice on.
-1-
How to optimize the bulk: Given that the auto-loader should avoid having to
update itself,
Hello Mark,
the solutions to this are many, I'll tell you what my current approach is.
First minimal loader, no code or elements but the ones needed for loading
the mainstack and a possible version check of the loader itself that may
prompt the user to download a new loader in case you need an
Hi Andre:
Good information. Couple of more questions:
-1- On first use, do you require connectivity in order to cache the main stack?
I assume yes, right?
-2- In the BOM stack approach, how do you control versioning and dependency?
(i.e. resource stack X must be downloaded with widget Y,
Mark,
I am no expert on such issues but my best answers are:
-1- You can bundle a copy of your main stack with your installer, so you
have an environment with all the needed files for the first run.
-2- The way I do is using order of download, dependencies are downloaded
before the stuff that
