|
imagine A project call B project. to work correctly, B needs A to pass him macros. let's imagine for example that B is a project in which you do some SVN steps, VS .NET steps and NSIS steps. you need at least to pass the path to the csproj (or vbproj or sln), the SVN URL, etc.
the person who launch B from A know macro he has to pass, but maybe he doesn't know their names. so in my custom step i added a tab and properties (checkbox, etc...) very easily, but i have to transform the step properties (data entered by the user in the fields) to macros, launch a visbuildpro instance, passing the macros, retrieving the status of B, etc... all this in VBScript. it is not so hard, but it would have been handy to have an "advanced visbuildpro step".
i join a doc to explain with pictures.
|
09-13-2006, 10:20 AM
Threaded Mode