Process Debugging Workaround for K2 blackpearl 0807

  • 16 February 2021
  • 0 replies
  • 3 views

Userlevel 3
Badge +8
 

Process Debugging Workaround for K2 blackpearl 0807

KB000308

PRODUCT
K2 blackpearl 0803 to 0807
BASED ON
K2 blackpearl 0803
TAGS
K2 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 0803 developers are able to debug server events with custom code in the same project as the process. However, in K2 blackpearl 0807 enhancements and optimizations to the memory usage now require that the custom code be referenced as an external assembly to allow debugging to be done.

 

 

Error Scenario

A K2 blackpearl 0807 process has a K2 Server Code event, with custom code additions. The process deployment goes into error and the developer attempts to debug using K2 designer for Visual Studio. The following dialog will display indicating that an error has occurred, disalllowing debugging.

The error message is as follows:

  • The following breakpoint cannot be set: (EventItem in Extender Project). The Common Language Runtime was unable to set the breakpoint.

 

Resolution

Note: A degree of technical know how and familiarity with the Microsoft Visual Studio Project System would be an advantage.
To resolve the issue, do the following:
  1. Start a new C# Project > Add a code file
  2. Copy the custom code from the K2 Server event and paste it into the new project
  3. Give the file a name and compile the code as an assembly (*.dll)
  4. Open your K2 blackpearl project, and add the assembly as a reference
  5. Debug your code

 


0 replies

Be the first to reply!

Reply