Component Project (DATAFLOW Designer)
This Reference Article has been written for Version 2.1 of the DATAFLOW Software. For Previous Releases use the version selection in the navigation bar at the top of this page.
Component Project
A Component project is used in the DATAFLOW Designer to move a sub-component in a system design to a separate project.
The root element of the Component project is always the component context with a single component element. It works similar to the system context and system element, but allows to be mapped into a system architecture.
Component projects can only be created in a new solution separate from the solution that holds the system project.
Create Component Project
A component project can only be created when a new solution is created. A solution can contain a single component project.
Component Project Creation
Configure Component Project
When a component project is created, the following must be configured:
- Project Name
The name of the Project in the solution folder. It must be unique and must not contain any characters invalid for file names such as # % and $. It should not contain spaces. - Root Namespace
The root namespace is used for all code that is generated from this project. - System Context Name (optional)
If a name is set, this will be added to the namespace for all generated components. Normally, this can be left empty. - System Name
The name of the system in the DATAFLOW Designer. - Type Namespace (optional)
If a namespace is set, this will be added to the namespace for all generated data types. It is also possible to use type groups to achieve the same and leave this field empty.
All names and namespaces can be changed later and are not fixed after project creation.
Initial Component Project Configuration
Component Project Elements
In a component project, all element types can be used. The component context, diagram and component element can not be deleted.
The root type group can not be deleted.
Component Project Constraints
Build Configurations and Build Toolchain Configurations can be assigned to the component element or any system component or active container as long as there are no nested build configurations.
Component projects can reference library projects.
This Article has been written based on V2.1.1 of the DATAFLOW software.
Latest update 2023-06-01 by WUM.
Comments
0 comments
Please sign in to leave a comment.