Change data folder name for uncompressed setups

[lbertoldi]

Hi there, I'd like to share some files among different setups, mainly the prerequisites (e.g. the .NET fw).
I place them in a "common" folder in the root of my setup exe and I can run it using $SETUPPATH$\common\myreq.exe
But when I build each setup in uncompressed format, I get the same "data" folder for each one. So if I deploy each package in the same folder, their files are messed up.
On to the questions:
1. can I change the output "data" folder name? e.g. data_setup1, data_setup2, ...
2. if the answer is no, is it safe to mix the "data" folder contents?
Thanks

[FrancescoT]

Dear User,

>> 1. can I change the output "data" folder name? e.g. data_setup1, data_setup2, ...
No you can't.
>> 2. if the answer is no, is it safe to mix the "data" folder contents?
No it is not.

You could use Web media blocks to share components between different apps.

Regards

[lbertoldi]

Can you please explain how can I use web media blocks for this? I do not clearly understand how they work or how can I create them. Remember I need to distribute them with my setup, I do not want to download them.
Also, if I cannot mix the setups in the same folder, how am I supposed to use some shared component? Relative paths?
Thanks

[FrancescoT]

Dear User,

if you can't use file download WEB MEDIA BLOCK is not the solution.

I may suggest to you the following, obviously you could modify it to suit your specific needs;

- Create a New separate project that just copies your specific runtimes setup files.
- Modify your script and remove all code (dialogs, installation flow code as Apply Install and so on) and leave with it, just the code that effectively copies to a specific target dir, your runtime installation files. You could also take advantages of NATIVE ENGINE setting, to execute it outside MSI engine.
- The target dir could be hard coded or if you prefer, using a REG KEY, using a customized dialog or whatever other way that you like.
- Optionally you could affine your code, in order to copy on the target only those runtimes that are not already present.
- Build the project and include and run it, in each real Project that shares or requires these runtimes.

Doing this you should be able to solve your needs.

Regards