Navigation: Actions > Server > COM+ Component Action |
|
The COM+ Component action creates a step to create, modify, delete, and report on COM+ components.
Notes:
• | See the Server.bld sample for a project utilizing this action. |
• | This action requires a Windows 2000 (or a newer version) install with COM+ installed. |
• | By default, this action is not displayed (existing steps will still be displayed in the Step panes and will build normally). To show all hidden actions, right-click in the Actions pane and choose Show Hidden. |
Component tab
Operation: The operation to perform, which can be Add, Modify, Delete, or Report (required).
Computer: The computer whose Component Services catalog will be updated (optional). Use blank or My Computer for the local computer, or select or enter a remote computer name (the list is prepopulated with all computers that have been added to the Component Services console on the local computer).
Application: The application name to modify (required). The list is prepopulated with all existing applications on the local computer if the Computer field is empty or equal to My Computer; click the Refresh button to refresh the list from a remote computer name in the Computer field.
Enter an asterisk (*) to update all matching components in all applications on the computer (cannot be used with the Add operation).
Also, a regular expression can be entered to match multiple applications.
Component: The component to add or modify (required). When adding, this must be the full drive, path and filename of the component to be added. For other operations, this can be the DLL filename or a component ProgId. An asterisk (*) can also be entered to modify, delete, or show all components in the specified application(s). When adding a component, if the type library is in a separate file and/or there is a proxy-stub DLL, enter each filename separated by semicolons in this field: <component filename>;<type library filename>;<proxy-stub filename>.
Or a regular expression can be entered to match multiple components.
Install as event class: When adding components, if unchecked, the action installs all components (COM classes) from the DLL file in the Component field into the specified COM+ application and registers the components in the COM+ class registration database as configured components. If checked, the action will install event classes from a DLL holding dummy implementations of the event classes.
Transaction support: Transaction support option. If Default is chosen, the default or value configured in the component metadata will be used.
Synchronization support: Synchronization support option. If Default is chosen, the default or value configured in the component metadata will be used.
Transaction timeout: Component-specific transaction timeout value for transactional components (optional). If left blank, the default (computer-level) transaction timeout will be used.
Enable Just In Time activation: Whether to enable JIT for the component.
Note: Some combinations of properties are not valid (for instance, Transaction support of Disabled and Synchronization support of Supported', but this screen does not prevent invalid combinations from being selected, and invalid values will be ignored when the properties are assigned. See the link below to determine valid property values or view the component property pages in the Component Services Explorer to see the valid combinations.
Note: See the Server.bld sample for a project utilizing this action.
This tab can be used to set additional properties of the component. See the MSDN help topic on the Components collection for the list of available properties and values.