Microsoft .NET Framework issues

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

1.0 Known problems and workarounds
   1.1 ObjectNotFoundException occurs while inserting verification point on ErrorProvider, HelpProvider and ToolTipText controls in .Net
   1.2 Scroll events do not work properly for some .NET Controls
   1.3 Problem generating the config file without .Net 1.0 framework installed on the test system
   1.4 Unable to play back .Net scripts stored in the network
   1.5 Functional Tester fails to identify controls on Win32, .NET, HTML, Siebel, and SAP applications.

1.0 Known problems and workarounds

1.1 ObjectNotFoundException occurs while inserting verification point on ErrorProvider, HelpProvider and ToolTipText controls in .Net

This occurs if you create a data verification point on ErrorProvider, HelpProvider and ToolTipText controls while recording in .Net.

Workaround: Create properties verification points on these controls in .Net.

1.2 Scroll events do not work properly for some .NET Controls

The problem is with the GetScrollBarInfo method of the Win32 API. It does not return the correct result if visual styles are enabled.

WorkAround: If you disable/comment the Application.EnableVisualStyles() line from the application codebase, Rational Functional Tester works fine. In VS2005 this is the first line in the source code of the test application's Main() method.

Note: This problem occurs only on WindowsXP or Windows 2003 platforms.

1.3 Problem generating the config file without .Net 1.0 framework installed on the test system

You cannot generate the config file for an application compiled with .Net 1.0 Framework if the test system does not have .Net 1.0 Framework installed.

Workaround: To generate a config file, you must install the 1.0 framework on the test system first. Then, use one of the following commands:

Otherwise, you will need to write a config file for the application manually.

1.4 Unable to play back .Net scripts stored in the network

The project in the network may not have Full Trust permission in the local computer due to its security policy. A RuntimeSecurityPolicyException message is displayed in the playback log or in the RFT debug log.

Workaround: Perform the following:

If you still continue to see the message, perform the following steps:

    1. Click Tools > Internet Options in the Internet Explorer window.
    2. In the Security tab, select  Local intranet zone.
    3. Click Sites.
    4. In the Local Intranet dialog box, click Advanced.
    5. Uncheck Require server verification (https:) for all sites in this zone.
    6. Specify the project path and click Add.
    7. Click OK.

1.5 Functional Tester fails to identify controls on Win32, .NET, HTML, Siebel, and SAP applications.

This happens when .Net Framework in not installed on the test system.

Workaround: Install .Net Framework and run the Install.bat file to register the required DLLs from the <Functional Tester installation directory>\SDP70\FunctionalTester\installscripts directory.