ViewArticle

[Collapse]Automated Build Studio FAQ
  Can I use the same macro to build different versions of my product?/viewarticle/8709/
  Can my macro run operations defined in a separate macro?/viewarticle/8711/
  Can "Compile..." operations obtain the output from the compilation process?/viewarticle/8716/
  How can I handle errors that occur in my macros?/viewarticle/8715/
  How can I notify team members about the build success/failure?/viewarticle/8714/
  How do I increment my build version number?/viewarticle/8710/
  Is there integration with Visual Studio? Does this mean Automated Build Studio just functions like MSBuild editor?/viewarticle/8712/
  What are the limitations of the demo version?/viewarticle/8713/
Updated: 11/1/2010 Applies To: Automated Build Studio Rating: GoodGoodGoodGoodGood 16 vote(s) Click to rate: PoorNot badAverageGoodExcellent
Q.: Can I use the same macro to build different versions of my product?

A.: Yes, you can. The best way to do this is to use multiple configurations within your macro. A macro configuration includes the following:

  • property values of all operations that exist in the macro;
  • values of all custom constants and stored variables that are defined in the macro;
  • the Environment attributes of all custom constants and variables (including the stored variables) that are defined in the macro.

Therefore, you can have one structure of operations within your macro for all of the product versions you need to build, and have an individual macro configuration for each of these versions. For instance, one configuration for the Debug version, another configuration for the Release version, etc. To learn more about this, see Using Macro Configurations.



© 2017 SmartBear Software. All rights reserved.
Email Send feedback on this document