Modeling a Visual Basic unit file in a model (Visual Basic code)
A Visual Basic unit file is modeled through a Modeler Package, Class, Data Type or Interface.
To model a Visual Basic unit file in a model:
1. In Modeler, create the Package, Class, Data Type or Interface you are going to use to model the Visual Basic unit file.
2. Right-click the Package, Class, Data Type or Interface point to Links > Stereotypes, and then click VB Unit.
3. Set the standard properties of the Package, Class, Data Type or Interface as required. For more information, see the related links below.
4. Open the Package's, Class', Data Type's or Interface's Property Pages, and click the VB Unit tab.
5. If you do not want ACS to generate the unit file in the default location using the name of the Package, Class, Data Type or Interface:
◦ Specify the location and name of the unit file you want to generate through the VB UnitLocation tag definition.
If you specify a name only, ACS generates the unit file in the ACS target folder using the specified name.
If you specify a location and name, ACS generates the unit file to the specified subfolder of the ACS target folder using the specified name for the unit file. For example, if you specify MyUnitFiles\UnitFile1, ACS will create a subfolder named MyUnitFiles and create a unit file named UnitFile1.
6. If you want to specify import clauses, set the value of the
VB Imports tag definition to the import clauses you want to generate.