Chained Package as Optional Component - Advanced Installer Community

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!

niknak
Posts: 7
Joined: Wed Jul 06, 2011 4:57 pm

Chained Package as Optional Component

Hi there,

Is it possible to add a chained package msi to the Organization / Features & Components list?

I have one in my install package that i'd like to be selected during this step as to whether or not it should be installed but I can't see it in the list at the moment and there seems to be no way to add it.

Nick.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Chained Package as Optional Component

Hi Nick,

In the chained package Options pane you can set an install condition. This condition can use any feature or component you want.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
niknak
Posts: 7
Joined: Wed Jul 06, 2011 4:57 pm

Re: Chained Package as Optional Component

cosmin wrote:Hi Nick,

In the chained package Options pane you can set an install condition. This condition can use any feature or component you want.

Regards,
Cosmin

That's excellent thanks, worked great.
niknak
Posts: 7
Joined: Wed Jul 06, 2011 4:57 pm

Re: Chained Package as Optional Component

cosmin wrote:Hi Nick,

In the chained package Options pane you can set an install condition. This condition can use any feature or component you want.

Regards,
Cosmin

Hi there,

Unfortunately it wasn't working like I thought it was, my current condition for the chained package install is...

((&mychainedpackage) AND (Not Installed))

"mychainedpackage" is defined as a feature within the Organization section but there are no components added to the feature, it's completely empty, does this matter? I do not have anything relevant to add to it as a component but I could make a dummy file.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Chained Package as Optional Component

Hello,

You can try the following condition:

Code: Select all

&mychainedpackage=INSTALLSTATE_LOCAL
This condition will be true only if the feature "mychainedpackage" will be installed locally. If the feature is not selected for installation the condition is false.

Also, the feature will never be installed if it's empty.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
niknak
Posts: 7
Joined: Wed Jul 06, 2011 4:57 pm

Re: Chained Package as Optional Component

mihai.petcu wrote:Hello,

You can try the following condition:

Code: Select all

&mychainedpackage=INSTALLSTATE_LOCAL
This condition will be true only if the feature "mychainedpackage" will be installed locally. If the feature is not selected for installation the condition is false.

Also, the feature will never be installed if it's empty.

All the best,
Mihai

Hi there,

I have tried the suggested, both on its own as...

&mychainedpackage=INSTALLSTATE_LOCAL

and

((&mychainedpackage=INSTALLSTATE_LOCAL) AND (Not Installed))

but neither of them seem to be installing the module, it's not installed under any circumstance now. Either as a full install, or custom with it selected.
niknak
Posts: 7
Joined: Wed Jul 06, 2011 4:57 pm

Re: Chained Package as Optional Component

I've just been trying the following condition...

((&mychainedpackage = 3) AND NOT (!mychainedpackage = 3))

and it appears to be working!

Return to “Common Problems”