Microsoft KB Archive/917559

= FIX: The debugger moves to the next .line directive when you set a breakpoint on a statement and the statement is related to a .line directive that does not contain a column range in the .NET Framework 2.0 =

Article ID: 917559

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft .NET Framework 2.0

-



SYMPTOMS
Consider the following scenario. In the Microsoft .NET Framework 2.0, you set a breakpoint on a statement. The statement is related to a .line directive that does not contain a column range. In this scenario, the debugger moves to the next .line directive. This behavior occurs if the following conditions are true:
 * The first .line directive has no column range.
 * The second .line directive has a column range.

For example, the debugger moves to the second line when you set the breakpoint on a statement that is related to a .line directive. The following Microsoft intermediate language (MSIL) code example illustrates this scenario. .line 5 .line 6: 8, 14 Note If both .line directives have no column range, the debugger behaves as expected and stops on the first line.

This problem typically occurs if the following conditions are true:
 * A compiler creates MSIL code.
 * You debug the MSIL code in a managed code debugger such as Microsoft Visual Studio .NET.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note   In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

The Microsoft .NET Framework 2.0, itanium-based versions


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about this problem in the Microsoft .NET Framework 1.1, click the following article number to view the article in the Microsoft Knowledge Base:

889188 FIX: Breakpoint does not work correctly on a .line directive that does not have a column range in the .NET Framework 1.1

Additional query words: KB889188 VS2005 ilasm .line directive column range

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB917559

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.