Hi there,

I have implemented pre-compile variable evaluation in my application to
create a "Demo" version of my application with limited functionality. I
would like to use this easy method within the setup package too, for
example, my "Demo" version cannot load additional plug-ins other than the
ones that are embedded into the application, so I need to be able to
distribute a different plug-in configuration file for both the "Demo" and
"Full" version.

Is it possible to either,

A) Make 2 setup projects, and have each version compile a different
version of the application by changing the global compile variable
"THISISADEMO" to "True" for the "Demo" version and "False" for the "Full"
version. This way I can specify unique configuration files for each setup
package.

or

B) Have the setup project dynamically evaluate this variable and
change the package automatically.

Thanks loads in advance for any helpful tips! Cheers!

Nick.

Hi Nick,

I think both of them are possible. For solution A, you need to manage two
setup projects but it is not very hard to do this. And it is easy to
understand. For soultion B, you may need to add some code in the Custom
Action of the setup project, evaluate the variable and set different
configration file. This may need more work on the setup project.

Luke

Hi Luke,

Cheers, I think I shall try solution A then :-) Thanks.

Nick.

"[MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Nick,
>
> I think both of them are possible. For solution A, you need to manage two
> setup projects but it is not very hard to do this. And it is easy to
> understand. For soultion B, you may need to add some code in the Custom
> Action of the setup project, evaluate the variable and set different
> configration file. This may need more work on the setup project.
>
> Luke
>