VB Branding
32-bit Brandable Application SDK
Frequently Asked Questions 32-bit Brandable Application SDK
Below are a number of the most frequently asked questions received regarding the 32-bit Brandable Application SDK for Visual Basic 6.0. Please check here first before contacting us for support.

Q: If a brandable application is developed and packaged on computer A, then ported over to computer B, can the MABU be run on computer B to create the ABU for the brandable application?

A: Yes. Just as long as the files that are ported over to the computer with MABU installed are the files contained within the Support subdirectory of the directory in which the application was packaged.


Q: If a person possesses a copy of an ABU developed for brandable application A, can that ABU also be used to brand brandable application B?

A: No. Each ABU is constructed to work with a specific brandable application package.


Q: Will the MABU allow me to create an ABU for brandable applications that are packaged for distribution using setup development software other than the Package & Deployment Wizard that comes with Visual Basic?

A: No. This is a limitation of the Brandable Application SDK that is targeted for improvement in a near-future version.


Q: Will the MABU allow me to create an ABU for brandable applications that are packaged using multiple cab files?

A: Yes. The number of cab files existing in the application's setup files does not affect the ability for the MABU to generate an Application Branding Utility.


Q: How safe is it to develop brandable applications and to give them demo features using DemoBuilder?

A: Only slightly. With the right tools and training, an experienced software hacker can easily make a few changes to the branded demo application to convert it to a full-featured application. This is a limitation of the DemoBuilder feature that is targeted for improvement in a near-future version.


Q: Is any documentation available, such as "White Papers", to show how the Brandable Application SDK works in all its intricacies?

A: No, and they never will be made available. The techniques used by the Brandable Application SDK and its components are proprietary to Blue Aegis Software & Marketing, and are patent pending as of the date of this document's development.


Q: Can I add my own files, such as advertisements and ebooks, to Application Branding Utilities once they have been created for distribution?

A: No. They must be added outside of any cab archive created by the Application Branding Utility, and should be saved to the same directory folder in which the ABU's setup files are located.


Q: Is there a limitation to the number of times I can use the Brandable Application SDK in the development of brandable applications and Application Branding Utilities?

A: No. You are only limited according to your application development skills.