Release Notes

DevPartner Studio Professional Edition

Release 10.0.0


DevPartner Studio 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. DevPartner Studio helps developers detect, diagnose, and resolve software bugs, maximize code performance, and ensure optimal code coverage and testing.



Obtaining the Latest Release Information   back to top

If you accessed this document from the product media or from the program shortcuts on your desktop, you may not be reading the latest release notes. For the most recent information, go to SupportLine, Micro Focus's customer care web site. The first time you access SupportLine, you are required to register and obtain a password. After logging on to SupportLine, click the Product Documentation link on the left side of the page, then click the link for your product. You will find the latest release notes listed with the other product documentation.



Installation   back to top

For installing product updates obtained through the Micro Focus SupportLine Product Update web site, refer to the applicable product update readme document. For licensing, system requirements, supported environments, and installation information, see the Distributed License Management Licensing Guide and the DevPartner Studio Installation Guide.

DevPartner Studio provides installation and licensing guides in PDF format. Users can print any product documentation offered in PDF format by opening the document and using the Adobe Reader print options. The DevPartner Installation Guideis also accessible from the DevPartner installation media, by clicking on the "Read the installation guide" link on the initial setup page. These documents can be opened and printed prior to installation.

(If you do not have the Adobe Reader, you can download it from the Adobe Web site.)

Before installation, note the following:

Refer to the DevPartner Studio Installation Guide for more information on installation options.

Back to Contents


InfoCenter and PDF Manuals   back to top

Information about DevPartner is available through the InfoCenter option in the Start>Programs>Micro Focus>DevPartner Studio menu. For general product information, refer to the Understanding DevPartner manual and the DevPartner Studio Quick Reference guide available through the InfoCenter.

(If you do not have the Adobe Reader, you can download it from the Adobe Web site.)

Back to Contents


What's New in This Release   back to top

New in Release 10.0.0

Microsoft Visual Studio 2010 Support

DevPartner Studio 10.0.0 provides full Microsoft Visual Studio 2010 support. This includes full support the analysis of applications developed using Microsoft Visual Studio, and full integration into the Visual Studio 2008 IDE. Analyze, detect errors and perform static code reviews in new Visual Studio 2010 project types.

Microsoft Team Foundation Server 10.0 Work Item Submission

DevPartner Studio 10.0 supports submission of additional Work Item types to Microsoft Team Foundation Server 10.0. DevPartner Studio 10.0 automatically populates Work Item forms with selected session data for the issue work item type, as well as bug and defect work item types. Work Items can be submitted through both Visual Studio 2010 and 2008 when used with Microsoft Team Foundation Server 10.0 and the active Team System project supports the Work Item type.

Support for MSBuild

DevPartner 10.0 supports MSBuild to build any DevPartner project in Visual Studio 2010. MSBuild starts automatically whenever building a solution from the build menu.

.NET 4.0 / Common Language Runtime (CLR) 4.0 Support

DevPartner 10.0.0 lets you test and analyze any applications that leverage CLR 4.0, the common language runtime for .NET 4.0. CLR 4.0 support includes all DevPartner supported project types in Visual Studio 2010.

Experimental Support for Micro Focus Visual COBOL for .NET Projects

DevPartner now allows you to analyze Micro Focus Visual COBOL for .NET project types. This includes memory analysis, performance analysis, coverage analysis for managed COBOL for .NET projects. In-depth performance for COBOL for .NET projects can be done where standard disk I/O, network and other Microsoft standard .NET calls are used. Micro Focus Visual COBOL must be installed on the same computer as Visual Studio to enable the Micro Focus Visual COBOL for .NET project type for analysis.

Support is limited to experimental usage in this release, and no Code Review or native COBOL support is provided. DevPartner customers who wish to provide feedback on this capability should identify themselves through the Micro Focus SupportLine Customer Care web site.

Enhanced Performance Timing

DevPartner Studio Performance Analysis (PA) has been enhanced to more accurately track and measure overhead used by its instrumentation model while capturing performance metrics. These enhancements dynamically calculate PA performance overhead while it is running against a target application. This allows a more precise application performance measurement when comparing to clock (CPU) time.

Note that hardware and software interrupt architecture may impact performance timings and yield minor variances when compared to CPU time. Hardware and software interrupts execute Deferred Procedure Calls (DPC) and Asynchronous Procedure Calls (APC) instructions on the user thread being monitored in the target application, which is included in the target thread's timing. Also, since PA executes in the same target thread, the PA instrumentation model execution overhead lengthens the overall target thread execution time, which results in more opportunity for interrupts. The potential for interrupts occurring during a target thread execution varies depending on hardware and software on the machine executing the thread and on other machine activity.

Retirement of Integration with Micro Focus Track Record

Bug submission from DevPartner Studio to Micro Focus Track Record was removed in this release.

Retirement of Integration with Compuware Delivery Manager

Metrics submission from DevPartner Studio to Compuware Delivery Manager was removed in this release.

New in Release 9.1.0

Micro Focus Purchases Quality Solutions Products from Compuware

On June 1, 2009, Micro Focus purchased Quality Solutions products from Compuware Corporation. Newbury, England-based Micro Focus provides enterprise application management and modernization solutions. Compuware and Micro Focus will continue to collaborate to ensure that customers receive uninterrupted service and obtain the full value of both companies’ product capabilities.

While service and product quality are continuous during this transition, there are a few changes to consider:

Contact for product support

For the most recent product updates and information, go to SupportLine, the Micro Focus customer care Web site. The Customer Care phone number has not changed during this first release. In the near future, look for phone number and mailing address changes. You can find the new contact information posted on SupportLine in an updated Release Notes for each product and in future product release documentation.

Installation Path and Start Menu Changes

The default installation paths for the Quality Solutions products have changed from x:\Program Files\Compuware\<Product Name> to x:\Program Files\Micro Focus\<Product Name>. Correspondingly, the Start menu paths also have changed to reflect the move from Compuware to Micro Focus. If you have installed with a customized path, you will not experience any changes to the installation directory during migration.

Windows 7, Windows Server 2008 R2, Internet Explorer 8 Support

DevPartner 9.1.0 runs on both Windows 7 and Windows Server 2008 R2 operating systems. All existing DevPartner product capabilities from installation, operation, documentation, and integration with Visual Studio and other systems remain intact with these Windows operating systems. DevPartner also supports Internet Explorer 8 under these operating systems with limitations. See the item "Web Script Coverage and Performance Yield Incomplete Results on Internet Explorer 8.0" in the DevPartner 9.1.0 Known Issues for more information.

Internet Information Services (IIS) 7.5 Support

DevPartner 9.1.0 provides full analysis capability for ASP.NET applications and services hosted on Microsoft Internet Information Services (IIS) 7.5. Full DevPartner Support for IIS is across all supported DevPartner operating system platforms, including Windows 7 and Windows Server 2008 R2.

Project Selection in Code Review Batch Mode

With previous releases of DevPartner, all projects in a solution were reviewed when running Code Review using CRBatch from the command line. DevPartner release 9.1.0 lets you select specific projects to be reviewed. To do this, follow the /l parameter in the CRBatch command with the name of an XML file that contains a list of specified projects. DevPartner generates the XML file based on projects selected for the solution in the Code Review options.

Specifying individual projects within a solution for code review frees you from Visual Studio IDE dependence when you only want to process portions of a solution for code review. Running code review on selected projects in batch mode also gives you the flexibility to tailor code reviews on large solutions to only the desired areas of code. This can help shorten code review batch runs and streamline overnight code review batch processing.

Experimental Support for Micro Focus Studio Enterprise Edition (EE) COBOL for .NET Projects

DevPartner now allows you to analyze Micro Focus Studio EE COBOL for .NET project types. This includes memory analysis, performance analysis, coverage analysis for managed COBOL for .NET projects. In-depth performance for COBOL for .NET projects can be done where standard disk I/O, network and other Microsoft standard .NET calls are used. Micro Focus Studio Enterprise Edition must be installed on the same computer as Visual Studio to enable the Micro Focus Studio EE COBOL for .NET project type for analysis.

Support is limited to experimental usage in this release, and no Code Review or native COBOL support is provided. DevPartner customers who wish to provide feedback on this capability should identify themselves through the Micro Focus SupportLine Customer Care web site.

Compile, Instrument Unmanaged Code, Set Environments, and Build from the Command Line

With DevPartner 9.1.0, a single command lets you compile, instrument unmanaged code in a project or solution, and build the project or solution from the command line. The NMDEVENV command combines the code instrumentation and compile capability of the DevPartner NMCL command with build capability of the Visual Studio DEVENV command. NMDEVENV replaces the Visual Studio DEVENV command and gives you the flexibility to instrument, compile, and build solutions in batch processing and from the command line without multiple commands. NMDEVENV uses Visual Studio instrumentation options set for the project or solution being instrumented and built, ending the need to enter instrumentation options in command syntax.

Use NMDEVENV with the NMCL option to enable instrumentation, and the DEVENV /Build or /Rebuild switch. Specify the project or solution, and whether to build with debugging. Note that if Debug is used and you have multiple debug configurations, Debug must be in quotes and entered with a specific qualifier (for example Debug|Win32. No DEVENV IDE switches or other switches are needed.

NMDEVENV is located in the \\Program Files\ Common Files\Compuware \NMShared folder by default.

Examples

To build the debug configuration of a project with Error Detection instrumentation:

NMDEVENV /nmbcon sample.vcproj /build debug

To build the debug configuration of the sample solution with Performance and Coverage instrumentation:

NMDEVENV /nmtxon sample.sln debug

To build a Windows 32-bit debug configuration (if multiple configurations exist) of the sample project with both Error Detection and Coverage instrumentation:

NMDEVENV /nmbcon /nmtxon sample.vcproj "debug|Win32"

Back to Contents


Technical Notes   back to top

If you have Internet access, visit the DevPartner Documentation page on the Micro Focus SupportLine site to view the Micro Focus Knowledge Base for additional DevPartner Studio issues and other information. The Knowledge Base is updated with new information as it becomes available.

Code Review

Coverage Analysis, Performance Analysis

Error Detection

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 Technical Notes

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 Technical Notes

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 Technical Notes

Coverage and Performance Testing for Internet Explorer 8.0 Applications

Applies to Coverage Analysis and Performance Analysis

Currently, the recommended method for testing Internet Explorer 8.0 applications is to use the Web Script Coverage and Web Script Performance Utilities (Start > Micro Focus > DevPartner Studio > Utilities > Web Script Coverage for coverage testing and Start > Micro Focus > DevPartner Studio > Utilities > Web Script Performance for performance testing).

However, if doing Web site coverage or performance testing within Visual Studio is required, the following must be done.

Back to Technical Notes

Web Script Coverage and Performance Yield Incomplete Results on Internet Explorer 8.0

Applies to Coverage Analysis and Performance Analysis

Internet Explorer 8.0 (IE8) is supported for driving, testing, and profiling server applications, as well as for rendering of management reports, XML output, online help, and other general browser usage in DevPartner. However, IE8 in the parent/child process model compared to prior IE releases proved incompatible with the embedded script debugger used in DevPartner's browser-side profiling technique. If a test is performed with Code Coverage using an IE8 client, then no results are reported from the client. If a test is performed with Performance Analysis using an IE8 client, then the client report includes no script timings under the Source folder and unrelated or misleading system call timings. This remains a limitation of the DevPartner 9.1 release and will be corrected in a future maintenance release.

DevPartner customers who may be interested in participating in alpha testing to validate the resolution of this issue or other early experience programs should identify themselves through the Micro Focus SupportLine Customer Care web site.

Back to Technical Notes

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 Technical Notes


Known Issues   back to top

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

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



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

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

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

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

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 issue, run all coverage sessions that you intend to merge without rebuilding your application between sessions.

Back to Known Issues

Error Detection Memory Leak Reporting With Symantec Endpoint

Applies to Error Detection

Users of Symantec Endpoint may not be able to reliably detect memory leaks when using Error Detection. Symantec Endpoint loads a Dynamic Link Library (.DLL) file that interferes with Error Detection's ability to detect memory leaks. This issue does not occur with Symantec Endpoint release SEP 11 MR4 MP1a (11.0.4.4014) and later for the unmanaged client, but may exist still exist in release SEP 11 MR4 MP1a (11.0.4.4014) and later for the managed client.

To work around this issue, upgrade to Symantec Endpoint release SEP 11 MR4 MP1a (11.0.4.4014) or later for the unmanaged client.

Back to Known Issues

Unhandled Exceptions under BoundsChecker on Windows 7

Applies to Error Detection

When an application tested under BoundsChecker on the Windows 7 operating system encounters an unhandled exception, BoundsChecker is unable to prevent that application from terminating  immediately. On earlier releases of Windows operating systems, BoundsChecker retained control of the application long enough to obtain a final memory leak report. On Windows 7, the application simply terminates. The session transcript notes the termination, but does not report the exception itself, and does not generate memory leak messages about what may still be allocated in memory.

In these instances, a final memory leak report may not contain much useful data, because the application does not get the chance to perform an orderly shutdown.

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

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 collects data properly the next time the DCOM or COM application or component starts.

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

IIS May Stop Responding When Restarting in Visual Studio While Profiling a Web Project

Applies to Performance Analysis

If profiling an Internet Information Server (IIS) Web Project using Performance Analysis within Visual Studio, if any process that accesses the local IIS (such as the Visual Studio 2010 Help Viewer) and then Visual Studio is stopped, restarting Visual Studio and starting an IIS Web Project may cause IIS to stop responding. A message box with the following message may also appear.

"Thread ID out of range for Quantum, Please consult readme for advice."

Perform the following steps to workaround this issue.

  1. Stop Visual Studio.
  2. Start the Windows Control Panel, then select Administrative Tools.
  3. In Administrative Tools, start the Internet Information Service utility.
  4. Right-click to select the IIS Web Project site and use the menu to either restart the service, or stop and start the service.
  5. Exit the Internet Information Service.
  6. Restart Visual Studio and start the IIS Web project.

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

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

Profiling with Performance Expert in Visual Studio 2010 or 2008 on Windows 7 or Windows Vista

Applies to Performance Expert

To profile applications with Performance Expert in Visual Studio 2010 or 2008 on Windows 7 and Windows Vista operating systems, you must run Visual Studio with administrator privileges. To profile ASP.NET applications with Performance Expert in Visual Studio 2010 or 2008 on Windows 7 and Windows Vista operating systems, you must start the application under an account with ASP.NET administrator privileges.

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 a DevPartner supported version of Visual Studio 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


Contacting Micro Focus Customer Care   back to top

If ever you have any problems or you would like additional technical information or advice, there are several sources. In some countries, product support from Micro Focus may be available only to customers who have maintenance agreements.

If you obtained this product directly from Micro Focus, contact us as described below. If you obtained it from another source, such as an authorized distributor, contact them for help first. If they are unable to help, contact us as described below.

However you contact us, please try to include the information below, if you have it. The more information you can give, the better Product Support can help you. But if you don't know all the answers, or you think some are irrelevant to your problem, please give whatever information you have.

Contact

Our Web site gives up-to-date details of contact numbers and addresses. The product support pages contain considerable additional information, including the WebSync service, where you can download fixes and documentation updates. To connect, enter www.microfocus.com in your browser to go to the Micro Focus home page.

If you are a Micro Focus Product Support customer, please see your Product Support Handbook for contact information. You can download it from our Web site or order it in printed form from your sales representative. Support from Micro Focus may be available only to customers who have maintenance agreements.

Back to Contents


End of DevPartner Studio Professional Edition Release Notes

Copyright 2009, Micro Focus (IP) Limited. All Rights Reserved.

04/15/2010 05:17 PM