Code Fix: Setting breakpoints for debugging in K2 blackpearl 0807
KB000323
PRODUCTK2 blackpearl
SEE ALSOKB000308: Process Debugging Workaround for K2 blackpearl 0807
TAGSK2 Designer for Visual Studio
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
Introduction
In K2 blackpearl 0807 developers were unable to set reliable breakpoints. The breakpoint would be accepted, but when debugging the code execution would not cease where the breakpoint was set.
Error Scenario
A breakpoint is set for debugging purposes and this may be for a server event or client event. Once debugging is started, and the breakpoint is reached the following error is reported by Visual Studio: "The common language runtime was unable to set the breakpoint."
If the user ignores the error message and cancels it, then the breakpoint that was set is ignored during debugging.
 | Note: Breakpoints would be ignored for both Server and Client events. |
Error Resolution
This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error.
The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx.
The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx.
