Is there a wyInstall for initial installations?

The wyUpdate program looks like a great solution to my SW distribution problem.

But.... can it be used to perform the initial install? You could say the initial install is an update from nothing.....

I have a vb.net desktop app needs deployment on a registration or phased in basis.

I would like to send someone a small wyInstall.exe (as an email attachment) and under seperate cover a user authentication key. wyInstall would request the key from the user, confirm it with something coded or configured into the wyInstall. Then it seems like the wyInstall would simply do all the same things as the Update, but may have to create the initial software program directory.

Is this possible? Thanks Ray

Unfortunately this isn't possible quite yet. Many people use Inno Setup, NSIS, or WiX Toolset. These are all free and relatively easy to use.

Creating installers from wyBuild will be supported in the future, but it's still in the planning stages.

I was able to patch the update code in only three places to add the desired "initial install" capability. Without full knowledge of the overall update and build architecture, my solution is only a patch.

Basically, If the update program does not find a client.wyc file in its launch folder or in a hardcoded destination folder, it 1) creates a program destination folder that has been hardcoded and 2) auto generates a minimal client.wyc file with just enough information to a) ID the server URL and login and b) set its current version to 0.

Then when the rest of the update code executes, it simply copys down the 'lastest version' of the program.and Voila we are installed. The version 1 files must include everthing that is needed (aka installed), because there is nothing on the user machine but the minimal client.wyc.

The two hardcoded pieces of knowledge are the server URL and the missing program folder.I think you could pass these in as parameters, but the goal was to be able to send a new user a single file "InstallMyProgram.exe" as an email attachment. I did not want to complicate this by trying to add an initial (version 0) client.wyc file or deal with parameters.

Also I did not add any 'user validation/install key" protection to this patch, I have a limited access controlled audience situation where the sofwtare is password proteced.

I only have one user facing program so creating a hardcoded installer was not a limitation for me. I did not have to create a general purpose solution. I simply wanted to have a single program than performed installs and updates.I also wanted to make minimal changes to the source so I could easily maintain updates from wyDay.

Ideally, the wyBuild program, could be used to maintain the required initial hardcoded parameters (including an installation key if required), and create the custom wyUpdate program without the need to recomile the update source each time. But I leave that up to Wyatt...

If anyone is interested in this solution, let me know.

Send me the changes to the source you've made to my email wyatt@wyday.com. I'll take a look at it and try to integrate it into version 2.7 or 2.8 of wyBuild & wyUpdate.

Almost 2 years gone and still no 2.7?What's happening with this product 😢 I need the initial install feature.

Thanks, Robert

Hey Robert,

What's happening with this product

We make course corrections. For instance a large feature like initial installs, might get sidetracked for other large features (like updating silently from services). Hence the seeming delay of the initial install feature.

There have been 14 "minor" versions (coming on 15 version) of wyBuild 2.6 with over 180 new features & fixes.

wyBuild is still very much alive and we're releasing 2.6.15 very soon. wyBuild 2.7 is the version that immediately follows that.

I need the initial install feature.

We're working on it. In the meantime use Inno Setup, NSIS, or WiX Toolset. The initial install feature hasn't been a critical "must get done now" feature for the very reason that there are these 3 great open source installers. Hence the delays and other features getting done first.