In such cases, the graph shows one root reference from an object array and an independent reference from a String array. In contrast, the Object Reference graph for a C application typically shows a single root reference to the String objects. In some cases, CPU time attributable to the expression part of a For loop can be incorrectly attributed to the body of the For loop. This can occur in loops formatted so that the initializers, expression, and iterators appear on a single line, as in the example below.
If the body of the For loop appears to be consuming excessive CPU time, reformat your code so the initializers, expression, and iterators appear on separate lines, as shown below. If you attempt to run a coverage analysis, memory analysis, or Performance Expert session immediately after running a performance analysis session on an ASP. If Performance Analysis runs too slowly on a supported low-end PC for example, a MHz Pentium III , you can speed up performance analysis sessions by changing the processor scheduling to provide equal processing priority for background services.
NET 2. With ASP. To avoid this problem, run all coverage sessions that you intend to merge without rebuilding your application between sessions. If code coverage is enabled and you use Fault Simulator to add a source-based. NET fault where the code construction includes compound or nested source statements on a single line, Fault Simulator might be unable to properly evaluate the designated method call. As a result, Fault Simulator might not fire the corresponding fault as expected during the fault simulation.
As a workaround, break out the source statement into multiple lines of code. Consider the following examples:. When running coverage or performance analysis, Visual Studio may become unresponsive and then display the following error:.
In the context of this issue, you can ignore this code. If this occurs several times, make sure that Internet Information Server is running. If it is not running, exclude system DLLs and try again. If the problem persists, use DPAnalysis. Run DPAnalysis. For more information, see the topic Using DPAnalysis. On systems with both DevPartner Fault Simulator 1.
In some cases, when running Fault Simulator and Coverage Analysis sessions together on a managed standalone Windows application, the DevPartner Session Control toolbar may be unavailable. This will prevent you from using the Stop Recording , Take snapshot , and Clear all recorded data functions during the session.
If your Coverage analysis requires use of the Session Control toolbar functions, try one of the following workarounds:. There is a known issue that prevents Performance Expert from collecting lock data for methods that use the MethodImplOptions.
Synchronized attribute. Code Review has alleviated an "Out of Memory" issue for large applications. A side effect of this resolution is a flickering screen while a Code Review session is in progress. This is a known Microsoft issue, and is addressed in Microsoft Knowledge Base article number If you notice certain anomalous occurrences, you should install Service Pack 1 for Visual Studio or Visual Studio Indications can be the following:. If a C method contains conditional code of the form if condition Code following the else branch is ignored.
In some instances, DevPartner Studio intermittently displays the wrong source code line in the Description pane on the Problems pane following a code review. This problem is related to underlying Microsoft code. While it is intermittent and random, it does not impact the accuracy of code review results or the ability for DevPartner Studio to successfully perform a Go to Source operation for the rule in question.
As a workaround, use the Go to Source function to access the correct location of the source code related to the rule firing. Code review will only print reports to the default printer. When the Print button or menu option is selected in the code review problems pane, a dialog box appears.
This dialog box controls the settings for printing, and allows you to select a specific printer other than the one currently set as default. However, the report will only print to the default printer, regardless of which printer is selected. The work-around is to change the default printer before attempting to print reports from code review.
Some of the new syntax in the C 3. If DevPartner Studio and Rational XDE Plus are both installed on the same machine, it is possible that incomplete results might be generated during a code review. In this case, No Problems will appear on the Problems pane following a code review on a solution, rather than a complete list of rule violations that you expect to see.
DevPartner Studio will be unable to perform a code review in batch mode if the solution in question is integrated in a source control system. This is not a DevPartner Studio bug, but a Microsoft constraint. Source control error messages will be generated even if the Integrated Development Environment is run in Automation mode, such as how the command line interface runs. Solutions containing source code that has compilation errors will occasionally generate a misleading error message when you run a review from the command line CRBatch.
Installing Fault Simulator 1. EXE error message might display stating that the application has encountered an error or has referenced memory it cannot read. Click Ok and ignore this error. Buffer overrun protection, a feature of many antivirus packages, can cause intermittent crashes when profiling Internet Explorer and IIS. Errors such as the following may occur:. If you have anti-virus installed and encounter these errors, turn off your anti-virus package's buffer overrun protection feature or contact your anti-virus vendor for updated software.
If you install Microsoft Visual Studio Service Pack 1, you must reboot your machine after installing the service pack. On Vista systems with UAC enabled, if you run Visual Studio without Administrative privileges, the Mach5 driver required for performance profiling is not started.
Performance analysis will provide inaccurate data. To correct this condition, run Visual Studio as an administrator, as suggested by Microsoft, or manually start the Mach5 driver with the net start mach5 command.
There is a known issue with displaying data collected for static initialization of member fields of partial classes in which a constructor is implemented in a different source file than the statically initialized fields. In these cases the source view will show no data for the static member field initialization. This is because the data is attributed to the constructor of the partial class and not the assignment statement for the static initialization of the field.
If a source file only contains statically initialized member fields for a class, the source file will not be shown in the list of source files for the module in the results. When you build the BugBench sample on Vista, you must have Administrative privileges.
Vista will not allow the DLL to be registered if you lack sufficient privileges. To ensure successful monitoring of your application when using Wait for Process under the standalone version of Error Detection, the target names and paths must exactly match what you specified to Error Detection.
If you use an intermediary step that somehow changes the target names or paths, Error Detection may not recognize that your application has launched. You may discover Error Detection is not returning symbol information. This can be caused by having your symbol paths defined at the solution level rather than the project level. Define your symbol paths under Project Settings. If you attempt to open a legacy solution file, Visual Studio may display the following error message: The selected file is a solution file, but appears to be corrupted and cannot be opened.
The problem is due to an obsolete entry in the solution file written by an earlier version of DevPartner. You can safely remove this entry using Notepad. To remove the entry:.
The first time that an application is run with Error Detection, you may see a dialog from Microsoft Internet Symbol Store detailing their Terms of Use. You must accept the Terms of Use to continue, even if you have previously accepted these Terms of Use when running a different program that also required Microsoft symbols.
In some cases, when you profile custom Windows services while logged in through Terminal Services, you may not get session files. If this occurs on your system, you may be able to save the session data by specifying the full path and filename for the session file. For example:. However, if doing Web site coverage or performance testing within Visual Studio is required, the following must be done.
All mixed-mode or managed applications profiled under Error Detection either with or without instrumentation require API metadata to function fully and properly. This is regardless of whether you are using the. NET Analysis or. NET Call Reporting features. To generate API metadata for. To execute the file with elevated privileges, right-click the file and select the menu option to run the executable as Administrator. NET assemblies change or are updated on the computer profiling under Error Detection, such as after a new.
NET framework is installed. Execution time of this utility varies based on the number of. The first time that an application is run with Error Detection, you may see a dialog from Microsoft Internet Symbol Store detailing their Terms of Use.
You must accept the Terms of Use to continue, even if you have previously accepted these Terms of Use when running a different program that also required Microsoft symbols. The language selector chosen during installation affects behavior of installed resources, user documents and helpsets , and the language of the Code Review default rules database.
Localized user documents often may track behind the English version. Localized user documents in this first Simplified Chinese release are limited to Release Notes only. Its integration into Visual Studio is the one place where DevPartner Studio adheres to application locale instead of system locale. Japanese works this way too. This section presents known issues that apply to this release of DevPartner Studio. Click a category to view the list of issues.
Suite-wide Issues. Coverage Analysis. Memory Analysis. Performance Analysis. Performance Expert. See article number in the Microsoft Knowledge Base for a detailed description of the Data Execution Prevention feature. By default this is set to OptIn , which specifies that DEP is only enabled for essential Windows programs and services.
If a C method contains code of the form if condition Code following the else branch is ignored. User-defined hyperlinks that reference external files might not respond when clicked even though the target of the link is valid. You might encounter this problem if you attempt to click hyperlinks in either the Rule Set list or the Preview pane of the Edit Rule dialog box in the Rule Manager.
System DLL calls can be monitored for IE with Performance Analysis and server coverage occurs with Coverage Analysis, but correlating script debugging data does not generate.
Note this only occurs with Web applications in IE 7 bit. This issue will be addressed in a future DevPartner release. An inconsistency in Visual Studio's Presentation Host may cause a scenario where DevPartner cannot correctly determine which Internet Explorer bit or bit is being used. Session data can display in the Performance Analysis or Coverage Analysis viewer, however the viewer cannot be resized and can only be closed. Line counts and performance timings are potentially attributed to an entire OpenMP block, rather than being disbursed to individual lines of code.
This issue will be addressed in a future DevPartner WebSync or release. See www. Running Error Detection with Coverage Analysis against a managed or mixed mode bit application on a bit operating system does not produce Coverage Analysis data or a Coverage Analysis session file. To work around this issue, run Coverage Analysis without Error Detection when running bit applications on a bit operating system.
A conversion utility for Memory Analysis and Performance Expert session files created with releases prior to DevPartner Collected static initialization data may not display for partial class member fields that have a constructor implemented in a different source file than the statically initialized fields. In these cases, source view may show no data for the static member field initialization.
This is because the data is attributed to the constructor of the partial class and not the assignment statement for the static initialization of the field. If a source file only contains statically initialized member fields for a class, the source file is not shown in the list of source files for the module in the results. In some cases, when you profile custom Windows services while logged in through Terminal Services, you may not get session files.
If this occurs on your system, you may be able to save the session data by specifying the full path and filename for the session file. For example:. NET application. With ASP. NET, the executable name changes every time you rebuild the solution.
0コメント