There are two options that can be used to resolve this message.
•Move the project directory higher in the directory tree. Depending on security settings, this may not be possible.
•Map a drive letter to the project directory:
After performing one of these options, reload the MxV project from the newly mapped directory.
When this error is reported by Visual Studio, it usually indicates that the link between Visual Studio and the MxSuite has been broken. Use this procedure to fix the problem.
Sometimes after a software exception, certain panes or windows, such as the Notifications box or System Explorer are not visible. This is caused by a corrupted Layout.xml file. To fix the problem, select View->Reset Layout.
Memory profiling for regression tests is now built into MxVDev.
See the Default.rsp text file in the Utility subfolder in the MxSuite installation folder.
The default response file can be used as is, or copied to a local directory and modified as directed.
To use this file as is, execute this command from the Windows Command Prompt before running an MxVDev Regression Test:
"<path-to-mxvdev-root>\Utility\NmpCore.exe" @"<path-to-mxvdev root>\Utility\Default.rsp" /p "<path-to-mxvroot>\bin\MxVGUI.exe" "<path-to-regression>\RegressionFile.mxreg"
where <path-to-mxvdev-root> is replaced by the MxSuite installation folder and <path-to-regression> is the directory containing the regression file to be run.
By default, session logs are saved in the user's Documents folder. Send the logs to firstname.lastname@example.org for analysis.
Note: If a message appears stating that nmpcore is unable to register a callback, add the parameter "/register" to the command line before the /p. The /p and everything following must be the last items on the command line. This option requires administrator elevation.
This build error can occur when multiple versions of Visual Studio are installed. The error is logged in the build log file.
LINK : fatal error LNK1201: error writing to program database .......\SUT\MxVTarget.pdb'; check for insufficient disk space, invalid path, or insufficient privilege
To prevent the error, open the solution in Visual Studio and use the File->Save <solution> As command. Do not change the name of your solution. For example:
Visual Studio File Menu
Logging (reporting problems)