Re: (ROSE) Rose 2001 and VS-C++ Add-In

[Marcus Daiber]

Hello Vincent, I am indebted to you. Your solution works just fine. The problem is a naming convention in the .dsp file. There is a section, which of course uses the german equivalents of "source file", "header file" and "resource file". Changing those section names solves the problem. Of course your solution works, too. There is a fourth section in that "file"-tab. I think it should be translated to "external dependencies", is that correct? I want to rename that section, too, just to be save everything is understood by rose. regards Marcus ----- Original Message ----- From: Richard, Vincent To: 'Marcus Daiber' ; [EMAIL PROTECTED] Sent: Tuesday, January 30, 2001 12:38 PM Subject: RE: (ROSE) Rose 2001 and VS-C++ Add-In Hi Marcus,   I had somehow a similar case from a German customer. The RE process seems to work fine but don't reverse anything. I paste below the answer I gave him hoping you are in the same position. Please tell me if this helps.   Regards,      Vincent.   The answer involves the Microsoft Visual C++ project folder information. If you look at the "FileView" tab on the "Workspace" browser for a Microsoft Visual C++ project, you will see folder nodes under the tree item that represents a Visual C++ project. Microsoft Visual C++ automatically creates folders named "Source Files", "Header Files", and "Resource Files" in the english release. Note that these project folders do not represent folders of directories in the file system; they exist only to let the user do some logical file organization in a project.   In Rose 2001, by default, the Rose Visual C++ engine will only RTE files that live in the "Source Files" and "Header Files" folders. Therefore, if you organized your .cpp and .h files under other project folders, then the Visual C++ RTE engine will not see them.   To remedy this situation, you can tell Rose a list of Visual C++ project folders that should participate in RTE.   In Rose, double-click on the component in the Rose Component view that represents the Visual C++ project. The component will typically have the same name as the Visual C++ project, and have  a <EXE> or <DLL> stereotype. You will now see the Component Specification dialog. Click on the "VC++" tab.   Near the bottom is a property named "ProjectFolders". Edit this property to contain the list of Microsoft Visual C++ project folders (not file system directories) that should participate in RTE. Enter one folder name per line of text in the property editor. Note that you don't have to enter the names of subfolders. Only the root folders (like "Source Files") are involved.   By the way, two related new properties in the component specification are "HeaderExtensions" and "BodyExtensions". You can use these properties if your project uses extensions other than the standard ".cpp", ".h", etc. for C++ source code.     -----Original Message----- From: Marcus Daiber [mailto:[EMAIL PROTECTED]] Sent: Monday, January 29, 2001 10:49 PM To: [EMAIL PROTECTED] Subject: (ROSE) Rose 2001 and VS-C++ Add-In I am having a problem reverse engineering with Rose 2001e. I have a W2K SP1 system (german) and VS-Studio Enterprise 6.0 SP4 (german) on a Compaq PIII600 256MByte. When reverse engineering ROSE does not import a single class, however it scans a typelib and imports interfaces. I have the same problem with win98 (english). The W2K System was a clean install with no other software on the system except VS-Studio and Rose. I already ran VS before starting Rose, several reinstalles of all components, and whatever someone could think of. Rose 2000e works just fine and scans the VS-Projects properly. Did anyone experience similar problems and knows a work-around, except using Rose 2000? Thank you for any hint. Marcus Daiber