Known Issue: After installing K2 Five Fix Pack 19, deploying workflows in K2 Studio/Visual Studio fails

  • 16 February 2021
  • 0 replies
  • 4 views

Userlevel 5
Badge +20
 

Known Issue: After installing K2 Five Fix Pack 19, deploying workflows in K2 Studio/Visual Studio fails

KB002856

PRODUCT
K2 Five 5.0
BASED ON
K2 Five 5.0
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.

 

Issue Description

After installing K2 Five 5.0 Fix Pack 19, when you try to deploy workflows using K2 Studio or Visual Studio, the deployment fails. K2 Studio reports no errors and no warnings. Visual Studio reports errors like 'The type or namespace name [typename] does not exist in the namespace 'SourceCode' (are you missing an assembly reference?)'

Screenshots of the behavior:
K2 Studio
Image

Visual Studio
Image

 

 

Cause

After installing Fix Pack 19 (or later), K2 workflow definitions should target .NET Framework 4.6.1. The workflow definitions for existing projects may not be updated to target this new version of the .NET Framework, and therefore deployment fails when you attempt to deploy the workflow to a K2 server.

Workaround

To work around this issue, follow the steps below

  1. Use a text editor like notepad to open the .k2proj file of the project containing the workflow you want to deploy
  2. Find the following entry:
    <TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
    or
    <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
  3. Change that entry to the following:
    <TargetFrameworkVersion>v4.6.1</TargetFrameworkVersion>
  4. Save the *.k2proj file
  5. Open the project in K2 Studio/Visual Studio. Now you should be able to deploy the workflow

 


0 replies

Be the first to reply!

Reply