RADE

Customizing Visual Studio .Net

After installing the product on a workstation, the customization of Visual Studio .Net is enabled by default at startup. 2 CAA menu items in the File Menu: New CAA V5 Workspace... and Open CAA V5 Workspace...

Other CAA menu items are displayed only after opening or creating a CAA V5 Workspace:

By default, all add-ins installed on the machine are activated. You can choose to deactivate some of them using Tools/Add-in Manager...

You can deactivate add-ins during you current session (1rst column), or deactivate for next startup (2nd column).

	When first opening Visual Studio .NET, the dialog box opposite is displayed. It is strongly recommended to create the new keyboard mapping scheme. To do so, proceed as follows: From the Tools menu, select Customize.... The Customize window is displayed. Click Keyboard.... In the Options dialog box, create your shortcuts. Click OK when done.
	In this version, "CATIA Design Studio Add-in" is not yet available on Visual Studio .Net, and the CodeGenerator does not include the DialogBuilder. This functionalities for the moment are only available on Developer Studio.

[Top]

Mapping a CAA V5 File Tree

The integration principle we have chosen is that Visual Studio .Net uses the concepts of solutions and projects:

• The concept of "solution" of Visual Studio .Net is mapped with the concept of workspace used in CAA V5, this identifies a set of projects where developers write programs.
• "Projects" of Visual Studio .Net are identified as coherent pieces of software, they contain program and resources files and produce either a library (dll) or an executable. The correspondences between projects and CAA V5 concepts are:
  • Any framework leads to a project
  • Any module leads to a project

[Top]

Mapping Projects to Frameworks and Modules

From the File menu, select Open CAA V5 Workspace... The dialog box which is displayed lets you open an existing workspace in order to work with mkmk (what is proposed in our example) or with mkmk and the Workspace Manager (if installed). Specify the workspace root directory (e:\www\MyWorkspace in our example) and possibly the version of mkmk (CXR15 in our example), the choice of the version is not proposed if only one version is detected.

The first time a CAA V5 workspace is opened, a message is displayed informing the user that his workspace does not contain any generated projects.

• A new window is then automatically displayed in which the user can select the framework and module for which a project will be generated. Note you don't have to generate a project for all frameworks and modules that can be found in a workspace. For performance reasons on projects loading, and also for ease of use, we recommend that you generate projects only for the modules you are currently working on. Projects can be regenerated at any time (using Refresh whole Solution from Filetree/Refresh Active Project from Filetree in the Project menu).
  A file tree appears in the window which can be expanded/collapsed to respectively display or hide internal modules.
  Check any framework/module to select it for project generation.
• Tips:
  • If you check a framework, projects will be generated for it and for all the modules it contains.
  • Conversely if you check only a subset of the modules in a framework, a project will be generated for this framework and the checked modules, other modules will not be processed.

• Click OK to generate projects for the selected frameworks and modules. A log window is displayed while generating project information and once finished Visual Studio .Net displays this information. Here is the corresponding generated projects displayed in the Solution Explorer or in the Class View.

Setting the Current Active Project

For several commands of the RADE interactive dashboard, you will need to set a current active Project. For example, when you create a new class with RADE, you need to set the corresponding module where you can to create the class, as the current active project. To do this, select the module project in the Solution Explorer or in the Class View and activate the contextual menu with the right mouse button, then select the item Set as StartUp Project. Note that you can also select Set as StartUp Project in the Project menu.

[Top]

In Short

Now you are ready to work using both the Visual Studio .Net environment and CAA V5 tools. The next article we advise you to read is Working with Visual Studio .Net [1] where you will find explanations about how to use others commands. If you are familiar with mkmk commands or Workspace Manager commands, you will find the corresponding Visual Studio .Net menus and commands in Workbench Commands Mapping [2].

[Top]

References

History

Copyright © 2005, Dassault Systèmes. All rights reserved.