Known Issues

DevPartner Studio Professional Edition

Version 9.0.0

Copyright 2008, Compuware Corporation. All rights reserved.


DevPartner Studio 9.0.0 Professional Edition is a suite of tightly integrated development features. DevPartner Studio incorporates code reviewing, error detection, two kinds of performance analysis, coverage analysis, and a memory analysis feature all integrated into Visual Studio, as well as a system comparison utility. DevPartner Studio helps developers detect, diagnose, and resolve software bugs, maximize code performance, improve memory usage, and ensure optimal code coverage and testing.


Contents


Contacting Compuware Customer Support

Customer support is available as a Priority Support Service from 8:00 AM to 6:00 PM EST, Monday through Friday. For purchase or upgrade issues, select the Compuware Sales option when prompted.

For technical problems, from installation to troubleshooting, contact Compuware Customer Support online at:

Problem reports should include:

Back to Top


Known Issues and Technical Notes

This section presents known issues and technical notes for DevPartner Studio. Click a feature name or category to view the list of issues.

Suite-wide Issues

Code Review

Coverage Analysis

Error Detection

Memory Analysis

Performance Analysis

Performance Expert

Issues Related to Visual Studio or to Visual Studio Team System

System Comparison

Back to top


Using a 64-bit Application

Applies to Coverage Analysis, Memory Analysis, Performance Analysis, Performance Expert, and Error Detection

When running against a 64-bit application, you must change the Any CPU entry in your solution file to x86 or you will get this message: DevPartner is unable to test 64-bit projects.

Back to Known Issues

Packages Fail to Load or Installation Fails Due to Data Execution Prevention Setting

Systems with the Data Execution Prevention (DEP) setting configured as /NoExecute=Always On and the CPU's Execute Disable bit enabled might prevent DevPartner Studio from loading into Visual Studio.

See article number 875352 in the Microsoft Knowledge Base for a detailed description of the Data Execution Prevention feature.

System-wide DEP is set in the BOOT.INI file using the /NOEXECUTE option on the system boot partition. By default this is set to OptIn, which specifies that DEP is only enabled for essential Windows programs and services.

Setting this to AlwaysOn causes the DevPartner Studio installation to fail, and if the setting is changed to AlwaysOn after installation it will cause the DevPartner Visual Studio package to fail to load into Visual Studio.

If you set DEP to OptOut, be sure to include the Visual Studio executable (DEVENV.EXE for Visual Studio 2005 and 2008) in the list of programs and services that are not to run with DEP.

Back to Known Issues

No Integration With DevPartner Fault Simulator

The integration to the DevPartner Fault Simulator product does not work with DevPartner Studio 9.0.0. Users of Fault Simulator integration should use DevPartner Studio 8.2.

Back to Known Issues

MSI.EXE Error During Install or Uninstall

During installation or removal of DevPartner Studio, an MSI.EXE error message may display stating that the application has encountered an error or has referenced memory it cannot read. Click OK and ignore this error. The install/uninstall will continue without error.

Back to Known Issues

Deleting a DevPartner Code Review Session File

Applies to Code Review

A DevPartner Code Review session file can only be deleted if it is not the active session file in a solution. A Code Review session file remains active after it is closed until another Code Review Session file is opened. If a Code Review session file is active, the Delete menu item is not available from the Code Review context menu.

To delete a Code Review session file, close the session file and open another session file in the solution, then select right-click on the closed session file in the Visual Studio Solution Explorer and select Delete. If the session file is the only Code Review Session file in the solution, close and re-open the solution, then delete the Code Review session file using the context menu.

Back to Known Issues

Japanese Character Set Not Supported for Naming Analysis

Applies to Code Review

The Japanese character set is not supported for Naming Analysis in Code Review.

Back to Known Issues

Installation of Service Pack 1 for Visual Studio 2005 may be Required

Applies to Code Review

If you notice certain anomalous occurrences, you should install Service Pack 1 for Visual Studio 2005. Indications can be the following:

Back to Known Issues

Code Review Only Analyzes Tokens in the "If" Branch of C# Preprocessor Directives

Applies to Code Review

If a C# method contains code of the form #if condition ... #else ... #endif, Code Review processes the code as though it only consisted of the #if condition branch. Code following the #else branch is ignored.

Back to Known Issues

Referencing External Files in Rule Manager using Hyperlinks

Applies to Code Review

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.

Examples include:

<a href="C:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\Samples\Setup\html\Start.htm">Microsoft .NET Framework SDK QuickStarts, tutorials, and samples</a>"

<a href="file:///C:\Program Files/Microsoft Visual Studio NET/FrameworkSDK/Samples/Setup/html/Start.htm">Microsoft .NET Framework SDK QuickStarts, tutorials, and samples</a>"

Back to Known Issues

Visual Basic Code Containing Declare Statement with Alias Clause

Applies to Code Review

Any supported Visual Basic code that contains a Declare statement with an Alias clause will be bypassed in a code review when the DevPartner Studio API rules are used to scrutinize the code. This limitation is due to an accuracy issue regarding declared APIs that are also aliased. This limitation only pertains to Visual Basic Declare statements with an Alias clause. Any DLLImport attributes placed on Visual Basic or C# API methods declared as external will still be reviewed successfully.

Back to Known Issues

No Data for Certain Lines in Partial Classes in Visual Studio

Applies to Coverage Analysis, Memory Analysis, Performance Analysis, and Performance Expert

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 will not be shown in the list of source files for the module in the results.

Back to Known Issues

Session Manager Service Message Appears When Starting Visual Studio 2008 on Vista Ultimate SP1 32-Bit

Applies to Performance Analysis

When starting Visual Studio 2008 on the Windows Vista Ultimate SP1 32-Bit, an error message may appear indicating that DevPartner Performance Analysis failed to get the session manager service and that profiling will be disabled. This can occur when DPAnalysis cannot create an instance of the COM object CLSID: 163DF3E5-701A-44d9-9B82-59F4EADBBAA8. This issue will be addressed in a future DevPartner Studio release.

Back to Known Issues

Profiling System Services through Terminal Services

Applies to Coverage Analysis, Memory Analysis, Performance Analysis, and Performance Expert

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:

DPAnalysis.exe /cov /output c:\temp\MyService.dpcov /s MyService

Note: This may not work in all cases.

Back to Known Issues

Merging Coverage Files for ASP.NET 2.0 Applications

Applies to Coverage Analysis

You may be unable to merge coverage session files for ASP.NET 2.0 applications.

DevPartner Studio can only merge coverage session files from the same build of your ASP.NET 2.0 application. With ASP.NET 2.0, the executable name changes every time you rebuild the solution.

To avoid this problem, run all coverage sessions that you intend to merge without rebuilding your application between sessions.

Back to Known Issues

Administrative Privileges Required to Build BugBench on Windows Vista

Applies to Error Detection

You must have Administrative privileges when building the BugBench sample application on Windows Vista. Building the sample generates a COM DLL that must be registered. Windows Vista will not allow the DLL to be registered if without Administrative privileges.

Back to Known Issues

Opening an Application Requiring Microsoft Symbols

Applies to Error Detection

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.

Back to Known Issues

Error Detection Collects No Data for DCOM or COM-based Applications/Components

Applies to Error Detection

There are two situations in which DCOM or COM-based applications or components try to run under the restrictions of the aspnet account. By default, when a DCOM or COM application or component is launched from within an ASP.NET enabled Web page, it will run in the context of the aspnet account. For security reasons, the aspnet account is a restricted account (it is a member of the Users group and has equivalent privileges). In this situation your COM component will not have the security privileges required for Error Detection to function properly. To work around this issue, you must configure your DCOM or COM application or component to execute within the context of the interactive user (via dcomcnfg.exe).

To configure your DCOM or COM application or component to run under the context of the interactive user:

  1. Open a command prompt and run dcomcnfg.exe.
  2. Expand Component Services > Computers > My Computer > DCom Config.
  3. Right-click on your COM component, and select Properties.
  4. Select the Identity tab.
  5. Ensure that you have selected The interactive user.
  6. Click OK.

Error Detection will collect data properly the next time the DCOM or COM application or component is launched.

Back to Known Issues

Error Detection Still Locates Leaks and Errors with Modules Disabled

Applies to Error Detection

Error Detection will still report some Leaks and Errors, even if all Modules are OFF under the Error Detection Settings, because:

Back to Known Issues

CPU Time Charged to Wrong Line in "For" Loop

Applies to Performance Analysis and Performance Expert

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.

			using System;
			public class ForLoopTest 
			{
			   public static void Main() 
			   {
			      for (int i=1; i<=5; i++) 
			          Console.WriteLine(i);
			   }
			}

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.

			{
			   for (int i=1;
			        i<=5; 
			        i++)
			        Console.WriteLine(i);
			}

Back to Known Issues

No Synchronization Lock Data

Applies to Performance Expert

There is a known issue that prevents Performance Expert from collecting lock data for methods that use the MethodImplOptions.Synchronized attribute.

Back to Known Issues

Installing Visual Studio after DevPartner Studio Installation

If you install Visual Studio 2005 or 2008 after your DevPartner Studio installation, follow this two-step process to integrate the two products:

  1. Rerun the DevPartner Studio installation, selecting Modify. (On Vista systems, you must run Modify from the installation media. DevPartner's Modify option is not available through Control Panel > Add or Remove Programs on Vista systems.)
  2. Run the DevPartner Studio installation again, selecting Repair.

The second step is required to integrate the DevPartner Studio help system with the Microsoft help system.

Back to Known Issues

Localization Support in Team Foundation Server

Applies to Code Review, Coverage Analysis, Error Detection, Memory Analysis, Performance Analysis, and Performance Expert

When using DevPartner Studio with a localized version of Visual Studio Team System, in which the name of the WorkItemType Bug has been localized to a string other than 'Bug', DevPartner Studio will not be able create and submit bugs to the Team Project.

Back to Known Issues

New Settings Detected

Applies to the System Comparison Utility

System Comparison now checks for additional settings when comparing systems. If you compare a snapshot taken with a previous version of the System Comparison utility with a snapshot taken with DevPartner Studio 8.2 or later, these settings will be listed as missing from the older snapshot.

Back to Known Issues


DevPartner Studio Professional Edition Known Issues

Copyright 2008, Compuware Corporation

09/29/2008 01:29 PM