InstallAware

Hello,

when i am changing my InstallAware Project, ususally i change the version. But i also want the new version to be independent from the old project. I have noticed that when using the "Save Project As" Function in InstallAware, and saving the project with a new name in a new folder, it still has dependencies to the project it originated from. For example: If i have "testProjectV1.0" and, after changing, i save it as "testProjectV2.0" in a new folder, i won't be able to open "testProjectV2.0" after deleting "testProjectV1.0".

Is there anything to avoid dependencies between the projects and use "save project as" to save the project as a complete new one?

Thanks

Copy the entire project folder. Save As just relocates the core project file while leaving all other script and references intact.

MichaelNesmith wrote:Copy the entire project folder. Save As just relocates the core project file while leaving all other script and references intact.

well, thanks. i was hoping there is an alternative.

This is the proper way to do it (copying folders), your project file is allowed to have references to scripts etc. in other folders so this is as designed.

I see. But if i copy the project folder, open it in InstallAware and save it with a new name, the script-name is still the old one. This may be confusing. Is there a possibility to change the script name via Installaware?

Of course, right click the script file in the Project Manager window and save it as something else.

Note that with proper use of InstallAware - features such as Compiler Variables, dynamic branching of the setup script based on target system and other conditions in the MSIcode script, you really don't need to copy and clone your setup projects. That is so "old school" and will create you more overhead down the road.

Just learn to build everything off of the same project with build time customizations; better yet build a single setup that "morphs" at runtime intelligently.