We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

hoopoe
Posts: 6
Joined: Tue Jun 24, 2008 10:50 am

components manipulations

hi

what about next wishes:
- sometime i have to move/copy set of components from feature to another feature... and i have to move/copy it by drag'n'drop one-by-one... it takes a long time... what about allow to select few components and drag all of selected components to another feature?

- when i create several installation packages i have to make some kind of compatibility between them... the good way to make this is add to some packages "dummy" components... these components doesn't includes any resources... just register in windows installer database... later this component is checked by CompLocator and package makes decision about continue installation or abort. this way allows to avoid manipulation by product codes and allows to make some dependencies more flexible... (if this description of problem not clear - i can write real example) so, but i can't create empty component using GUI... did i missed something?

thank you

-- Sergey
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: components manipulations

Hi Sergey,
sometime i have to move/copy set of components from feature to another feature
For this you can follow these steps:
- go to the Organization page
- select the "Product" entry
- press SHIFT+F4 on your keyboard (it will show all the features, components and resources in the project)
- select the components you want to move and right-click one of them
- select the "Move to New Feature" context menu and select the target feature

Note that this allows you to only move components. Currently you cannot share multiple components, but I have added this improvement on our TODO list and it will be available in a future version of Advanced Installer. Thank you for your suggestion.
i can't create empty component using GUI... did i missed something?
Please note that Windows Installer does not support an empty component (most likely the resulted MSI will have validation errors). Also, you can use other criteria to detect other installation packages or components (for example you can search for a file or a registry entry).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
hoopoe
Posts: 6
Joined: Tue Jun 24, 2008 10:50 am

Re: components manipulations

cosmin wrote:For this you can follow these steps:
- go to the Organization page
- select the "Product" entry
- press SHIFT+F4 on your keyboard (it will show all the features, components and resources in the project)
- select the components you want to move and right-click one of them
- select the "Move to New Feature" context menu and select the target feature
great!!! it works!!!
i can't create empty component using GUI... did i missed something?
Please note that Windows Installer does not support an empty component (most likely the resulted MSI will have validation errors). Also, you can use other criteria to detect other installation packages or components (for example you can search for a file or a registry entry).

Regards,
Cosmin
hmmm... microsoft uses this way to detect installed products... look at file attached here... if you build .msi file - it could be installed without problems...

as i can see in MSDN docs only component name, directory and attributes columns in component table are mandatory... all other columns may be empty... and if user create this "empty" component and add it to FeatureComponent table - this component will be registered and later other product will be able to detect this using CompLocator table and AppSearch action...

hmmm.. while i write this message i got one more idea: what about add possibility to attach component to directory... actually component for directory is created in case when directory is empty... and after files are added to directory this component is removed... if AI allows to not remove such components - it would be enough for this wish

thank you

-- Sergey
Attachments
test2.zip
(1.66 KiB) Downloaded 489 times
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: components manipulations

Hi,
if you build .msi file - it could be installed without problems
Yes, this is possible. However, the MSI will have the ICE18 validation error. If the KeyPath column is empty, then the folder of the Directory_ column is used as the key path. Also, this folder must be empty in order to be the key path.

I'm not sure why you need to use an empty component. Why aren't you using a component which contains resources from your package?
after files are added to directory this component is removed... if AI allows to not remove such components - it would be enough for this wish
Please note that the component is removed because Windows Installer requires it. This is specified in the Component Table article in the MSDN:

"If the value is not null, then KeyPath is either a primary key into the Registry, ODBCDataSource, or File tables depending upon the Attribute value. If KeyPath is null, then the folder of the Directory_ column is used as the key path. Because folders created by the installer are deleted when they become empty, you must author an entry into the CreateFolder table to install a component that consists of an empty folder."

Basically, this means that the key path of a component can be a file, a registry entry, and ODBC Data Source or an empty folder. Therefore, empty components are not supported.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
hoopoe
Posts: 6
Joined: Tue Jun 24, 2008 10:50 am

Re: components manipulations

ok... got it

thank you

-- Sergey

Return to “Feature Requests”