Update Packs - Protect original setup.exe files?

[gsaunders]

In a previous installer I once used (Wise) whenever I wanted to create a new upgrade (full or patch) it would have me open up the previous msi and then it would save the new one in a new folder. So at all times I had the setups for each version.

As I am playing with InstallAware and don't see this sort of thing happening.

I basically create my initial build 1.0.

I then want to create an update to 1.5 so I just open the existing (original) install script, put in the appropriate entries in the update packs section and versions section and then build. This of course overwrites the original setup.exe... not sure what it does with the original script.

Is there anything special I need to be doing to maintain older / previous version of the script and resulting setup.exe file?

Since this is so different from what I was use to I don't want to start of wrong.

Thanks.

[mills]

I would recommend to treat each InstallAware project in association with your product versions.

So, if you have product versions 1 and 2, you should have associated InstallAware projects 1 and 2 respsectively.

You will need to point to your previous setup/msi at times with the latest version.

So, that's the summary. Let us know if you have more specific questions.

[gsaunders]

I would recommend to treat each InstallAware project in association with your product versions.

So, if you have product versions 1 and 2, you should have associated InstallAware projects 1 and 2 respsectively.

You will need to point to your previous setup/msi at times with the latest version.

So, that's the summary. Let us know if you have more specific questions.

So let's say I created version 1 and now I am ready to create version 1.5. Do I open version 1 in installware and then save as into a new folder representing 1.5 and then change settings needed for the new version 1.5?

[gsaunders]

So let's say I created version 1 and now I am ready to create version 1.5. Do I open version 1 in installware and then save as into a new folder representing 1.5 and then change settings needed for the new version 1.5?

Just following up... I want to make sure I am properly using InstallAware to handle my initial install along with future updates over the life of the product?

I couldn't find a step by step guide for doing the above so I am left not 100% certain of how to do this.

[mills]

The easiest way to go about it is to create a new folder that you want to create your new installer in.

In InstallAware, with your old project open, click the "InstallAware" button at top-left of screen, then Save Project As, naming accordingly.

That way, everything will be renamed properly (in terms of the project files) and you can make minor edits as necessary.

[gsaunders]

Thanks.

It gets a little confusing when I keep seeing the phrase: "A Single Script for Installs, Maintenance, and Uninstalls" so start thinking do I keep doing a save as for new versions or just keep altering the existing script and saving over it as I update it.

From what you are saying I need to keep doing save as for each new build to maintain a history as well as keep / save the resulting EXE files.

How would one know this if they were brand new to installer technology??? I couldn't find anything that stepped you through the process saying here is the way to do it or here is the best practice with InstallAware.

[mills]

"A Single Script for Installs, Maintenance, and Uninstalls"

Refers to the capability of a basic setup to Install the product, Maintain (change/modify installed features) and Uninstall.

I will be working on an introductory/getting started guide when I'm not caught up fielding forum questions.

For now, do just search the help and forums and ask questions and eventually it should be fairly intuitive. The questions that new users are asking are definitely welcomed and being considered to help ease the learning curve for installer technology.

[mills]

Just an update. I realized that all you really need to maintain older versions is the executable/output folder. I usually keep a previous version myself, particularly for testing and to change or refer to various codes. However, if you needed that data, you could open old MSI files with orca.exe to examine.

So, in terms of patching, you won't need old project files, only the executable.

For updates, you shouldn't need it either, since updates are a generic term for an executable file that can be downloaded and run on the end-user system. All you should need to change is the update.ini file. I would sometime use a separate project to create a properly formed update.ini with the update packs. However, you could really manage that all in the same project.

Updates and patches are more complicated parts of InstallAware. I'm still learning about them too, but I'd like to make sure their functionality is clear to you, so let me know if any of this needs clarification.

[gsaunders]

I think I just got confused again.

I think a step by step guide to creating a basic install, then updates with how you should save or save as and the recommended best practices on folder structures.

Then a step by step guide to creating a basic install, then patches, etc.

Then a step by step guide to creating "fill in the blank"

I know InstallAware touts being the easiest and most simple, but the learning curve can be steep for those not familiar with installer technology... and can be for those with more experience if they are use to something else.

I think InstallAware can make themselves standout in a huge way by providing step by step documents or videos of the various scenarios.... and realize you can't do EVERY scenario, but you can do a lot.

I also know there are some very standard things like authentication or serial number stuff that could really be helpful with clear step by step guides verses here is a sample... figure it out.

Anyway... the more you provide in documentation and how to guides the more appealing your product becomes.

[mills]

Have you read the white paper on it?

[gsaunders]

Yes... I have read all white papers and guides I can find and I have searched the forum over and over and over.

However I have yet to find a step by step definitive guide on doing certain things. I see a lot of this is how I got it to work or look at the sample type of responses.

Providing written guides, video based guides, and even having a monthly or bi-monthly online seminar and recording them would be helpful.

From a marketing standpoint providing this kind of help can attract even more customers.

Are you an Installaware employee? I ask because in a previous post you said you were still learning some things about installaware so i wasn't sure if you were an employee or a designate forum moderator or what.

Thanks again for your assistance.

[mills]

Yes, I am an employee. I was recently hired to help create much of the content you are looking for. Unfortunately at the time, detailed howto guides and KB articles are hard to come by, but they will be created as time permits and user needs are identified. Foremost on my list are detailed, useful documents on patching and updates, which are complicated subjects that definitely deserve better guides. I estimate that these should be created within a month or so.

[gsaunders]

So let's say I created version 1 and now I am ready to create version 1.5. Do I open version 1 in installware and then save as into a new folder representing 1.5 and then change settings needed for the new version 1.5?

Just following up... I want to make sure I am properly using InstallAware to handle my initial install along with future updates over the life of the product?

I couldn't find a step by step guide for doing the above so I am left not 100% certain of how to do this.

I know this is an older post of mine, but just ran into an issue dealing with this process and thought it would be better to keep it together with this post.

According to mills I should do the following if I wanted to keep my old scripts in tact so I can go back and look at them later... to keep a history:

The easiest way to go about it is to create a new folder that you want to create your new installer in.

In InstallAware, with your old project open, click the "InstallAware" button at top-left of screen, then Save Project As, naming accordingly.

That way, everything will be renamed properly (in terms of the project files) and you can make minor edits as necessary.

However... just today I noticed the following:

1) I create project under v1.0.
2) I later want to create an update so I do a file save as of the project into new folder v1.5.

I was thinking that it moved everything to that folder and I could make changes and they would all save in v1.5. I just found that the main script myapp.mia that under v1.0 is not really copied over doing the save as. Doing the save as left the myapp.mia in the v1.0 and in the v1.5 the myapp.mpr now references ..\v1.0\myapp.mia.

Sooo... I am really messing with my original scripts and NOT working from a new copy like I thought I was.

So it would seem the best thing to do would be to completely duplicate folder v1.0 into v1.5. I don't believe any of the original files held path information so this should work and allow me to keep all my scripts intact from previous versions. Why do I want this... I just like seeing the history of what I did and to help in learning the process that I may have followed over time.

Also... what if I just royally screwed something up and want to recover. If I use the save as into the new folder v1.5 and start editing I am really editing what was in v1.0 due to the ..\v1.0\myapp.mia found in the v1.5\myapp.mpr file.

Could a Installaware rep chime in here and let me know if I am accurate in my statements and what they recommend doing if one wants to keep all old scripts intact. I do also keep old versions of the files used for the installer in backup locations so if I every trully want to rebuild an earlier version I could by just moving the files to the correct source locations... I have only needed to do this once though so not a big deal.

Thanks for your feedback!

Greg

[giaviv]

Greg,

What I usually do is copy over the entire project folder.
Then, I use a software that has a search in files capability to search for the original path of the project and replace it with the new path.

[gsaunders]

Greg,

What I usually do is copy over the entire project folder.
Then, I use a software that has a search in files capability to search for the original path of the project and replace it with the new path.

Perfect... I did this and I had already fixed them manually... but will use a tool I have to search for this in a more automated fashion.

Thanks