Hi Gigi,
I have an application that's deployed under OEM relationships to a variety of customers with their own look and feel, which is server database driven, and need to create a variety of installation Kits with customer-specific naming conventions.
The .Exe file will always be the same and an installation Kit registry setting controls the CustomerID used to govern look and feel of the program. The installation and registry folders are always customer specific and there is a requirement that multiple OEM versions need to co-exist (run, install, update & uninstall) and operate independently on the same system.
I know that with previous versions of AI saving the project to a different name maintained awareness and there were conflicts between two kits deployed in that manner, so each kit needed to be recreated from scratch.
My kit is fairly simple and what I'm wondering is if there is an easy way to make changes manually in the AIP file, perhaps global search and replace on certain GUID's or special names, and if so can you give me some advice on the best approach.
All the best,
Norman
Suggested Articles
Hi Norman,
If you want to create a new project starting from an existing one then use "File->Duplicate..." main menu option. In this way new GUID's (for "ProductCode", components, etc) will be automatically generated by AI. Let me know if this is not what you are looking for.
Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
If you want to create a new project starting from an existing one then use "File->Duplicate..." main menu option. In this way new GUID's (for "ProductCode", components, etc) will be automatically generated by AI. Let me know if this is not what you are looking for.
Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
Perfect...don't know how I missed it, thanks!
Another question if you don't mind:
The OEM kits are simple, with only a single .EXE file and Check for Updates .exe & .ini files, two OEM Logo icons for network up & down and two folders, one with portfolioX.txt and another with bannerX.bmp files and each OEM package has unique a Application, Application Shortcut and Registry HKCU folders.
The question is under Organization there are a lot of names and items created and I'm wondering if I need them all, or at least GUID's for the many of them, or whether it is better to create a couple of top-level named GUID entries and organize (for example) files, folders and shortcuts under one and registry items under another, then name them with some form of OEM-Name syntax to make them unique (in addition to the new GUID's)?
Does that make sense and will it work or are there things I need to look out for and may be overlooking?
Thanks,
Norman
Another question if you don't mind:
The OEM kits are simple, with only a single .EXE file and Check for Updates .exe & .ini files, two OEM Logo icons for network up & down and two folders, one with portfolioX.txt and another with bannerX.bmp files and each OEM package has unique a Application, Application Shortcut and Registry HKCU folders.
The question is under Organization there are a lot of names and items created and I'm wondering if I need them all, or at least GUID's for the many of them, or whether it is better to create a couple of top-level named GUID entries and organize (for example) files, folders and shortcuts under one and registry items under another, then name them with some form of OEM-Name syntax to make them unique (in addition to the new GUID's)?
Does that make sense and will it work or are there things I need to look out for and may be overlooking?
Thanks,
Norman
Hi Norman,
That is the default package organization created by Advanced Installer. Components cannot be directly delete in the "Organization" page they are automatically deleted when all contained resources (files, registry, etc) are removed from the project.
For what operation you can made in the "Organziation" page please see following link:
http://www.advancedinstaller.com/user-g ... ation.html
For example you can rename components, move resources from one
component to other, etc.
Hope this helps.
Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
That is the default package organization created by Advanced Installer. Components cannot be directly delete in the "Organization" page they are automatically deleted when all contained resources (files, registry, etc) are removed from the project.
For what operation you can made in the "Organziation" page please see following link:
http://www.advancedinstaller.com/user-g ... ation.html
For example you can rename components, move resources from one
component to other, etc.
Hope this helps.
Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com