K2 Workflows result in an error state when opened after Visual Studio upgrade from 2012 to 2015

  • 15 February 2022
  • 0 replies
  • 0 views

Userlevel 4
Badge +16




 








K2 Workflows result in an error state when opened after Visual Studio upgrade from 2012 to 2015





























This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.






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



The Development environment was upgraded from Visual Studio 2012 to Visual Studio 2015. There are several K2 Workflows supplementing the .NET application. When attempting to open the K2 solution in Visual Studio 2015, it  displays an error. How do I continue developing new workflows and maintain existing workflows in Visual Studio 2015?



 



Symptoms



When you opening K2 Workflow in Visual Studio 2015 after upgrading from Visual Studio 2012, an error appears.

Troubleshooting Steps



To resolve this issue, remove the K2 Client Component 'K2 for Visual Studio 2012' through the K2 Setup Manager. Below are steps on how to do it.



 



How to remove K2 Client Components (K2 for Visual Studio 2012)



 



1. Launch the K2 Setup Manager from the K2 Installer.



2. Select Modify and click next.



3. Uncheck the K2 Client Component ‘K2 for Visual Studio 2012.’



4. Click next until the K2 Setup Manager finishes.



5. Now you should be able to open K2 Workflows using Visual Studio 2015 without an error appearing.



 



If you are not using K2 for SharePoint, uncheck SharePoint configuration when you reach the end of the K2 Setup Manager.









0 replies

Be the first to reply!

Reply