Installation and Integration > Debugging Your Application

Home > Getting Started Guide > Installation and Integration

Debugging Your Application

Source Path in Debug Sessions for Visual Studio 6 and Visual Studio .NET

Visual Studio .NET

Visual Studio .Net stores the path of the files found during a debug session and uses it in the next session. In such a case one of the following behaviors can result.

It looks in the paths that were provided in previous debug session for a new file it does not know.

It does a substitution of the beginning of the PATH. For example, if C:\build\ACISR16\NTS\SPAbase\PublicInterfaces\base.hxx is found in c:\AcisInstall\SPAbase\PublicInterfaces\base.hxx, then DevStudio automatically searches for C:\build\ACISR16\NTS\SPAbase\PublicInterfaces\dcl_base.hxx in c:\AcisInstall\SPAbase\PublicInterfaces\dcl_base.hxx

Object Package

Object customers have to reference the header folder once and then the "Case 1" (mentioned above) applies and all other header files are found automatically. Path information need not be specified again, unless the solution information has been removed.

Source Package

For Source package, Spatial delivers ACIS as it has been built. This includes the interfaces that are already part of the object package. Customers have to reference a source file once and then the "Case 2" (mentioned above) applies and all other files are found automatically. Path information need not be specified again, unless the solution information has been removed.

Visual Studio 6

The mechanism used in .NET can be applied, if you choose to save the .opt file at the end of your debug session.

Object Package

The following registry keys specify the source path search:

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Devstudio\6.0\Build System\Components\Platforms\Win32 (x86)\Directories] "Path Dirs"="C:\\Program Files\\Microsoft Visual Studio\\Common\\MSDev98\\Bin;C:\\Program Files\\Microsoft Visual Studio\\VC98\\BIN; ..... "Include Dirs"="C:\\Program Files\\Microsoft Visual Studio\\VC98\\INCLUDE;C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE; .... "Library Dirs"="C:\\Program Files\\Microsoft Visual Studio\\VC98\\LIB;C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\LIB; .... "Source Dirs"="C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\SRC;C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE; ....

These settings can be overridden by the environment variables: PATH, INCLUDE, DIR, SOURCE and using "msdev /USEENV". There is no concatenation between Registry key and Environment variables. By default, PATH, INCLUDE and LIB is set by vcvars32.bat delivered by Microsoft.

You have to set SOURCE to the ACIS include folder and add other folders if needed (for example the source path for MFC and so on) and use msdev with /USEENV. After this setting is done, the header files can be automatically accessed during the debug session.

Source Package

For Source package, Spatial delivers ACIS as it has been built. This includes the interfaces that are already part of the object package. At Spatial, the build is done in R:\, and we recommended that you use the subst mechanism to build your application to access ACIS source file during your debug session.

[Top]

© 1989-2007 Spatial Corp., a Dassault Systèmes company. All rights reserved.