wellilein
02-28-2011, 09:29 AM
Hi,
the initial problem is: some PCs have custom action installed, others don't. I am trying to fix this problem within the build script itself.
So far I have tried 2 approaches:
1. Changing VISBUILD_CONFIG_DIR
Setting the VISBUILD_CONFIG_DIR macro during the build script is not possible, because I can only change temporary, project or global macros, but not system macros.
2. Copying the action to VISBUILD_CONFIG_DIR
This seems to work in version 7.7. Is it possible that it didn't work in older versions? We needed a workaround with a restart of Visual Build in 6.x, which confused CruiseControl.
Actually I don't really like approach 2, because I'd eventually overwrite other custom actions with the same name used by other projects on the build server, sharing the same visual build installation.
Any suggestions on this? Thank you.
the initial problem is: some PCs have custom action installed, others don't. I am trying to fix this problem within the build script itself.
So far I have tried 2 approaches:
1. Changing VISBUILD_CONFIG_DIR
Setting the VISBUILD_CONFIG_DIR macro during the build script is not possible, because I can only change temporary, project or global macros, but not system macros.
2. Copying the action to VISBUILD_CONFIG_DIR
This seems to work in version 7.7. Is it possible that it didn't work in older versions? We needed a workaround with a restart of Visual Build in 6.x, which confused CruiseControl.
Actually I don't really like approach 2, because I'd eventually overwrite other custom actions with the same name used by other projects on the build server, sharing the same visual build installation.
Any suggestions on this? Thank you.