This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. 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.
K2 blackpearl is compatible with servers and development computers on which the Microsoft .NET framework v3.5 and related service packs are installed. However, K2 blackpearl 0807 and prior releases are compiled using the .NET framework 3.0 and are not aware of or take advantage of the newer assemblies present in the .NET 3.5 framework.
|Note: This article applies to all K2 components, including runtime (server) components and design-time components. Server and design-time components will continue functioning as expected with the .NET 3.5 installed.|
In order to deploy processes from the K2 Designer for Visual Studio 2005 when you have the .NET framework 3.5 or greater installed it is recommended that you do not reference any .NET framework 3.5 assemblies. The .NET 3.0 and 3.5 frameworks use the same version of the Common Language Runtime (CLR, v2.0.50727), and while many of the assemblies in the .NET 3.5 framework are the same version as their counterparts in the .NET 3.0 framework, there are new assemblies that offer new functions. These new assemblies may or may not be compatible with the K2 Server.
If you do reference .NET 3.5 framework assemblies, you must ensure that the .NET 3.5 framework is installed on all development computers that are used in process design as well each K2 server used across all environments, such as Production, QA/Test, Development. You should fully test that the v3.5 assemblies function as expected in your processes before deploying to a production environment.
|Note: As of K2 blackpearl 0807 the K2 Designer does not support Visual Studio 2008. K2 is a member of the Visual Studio Industry Partner (VSIP) program and support for the latest version of Visual Studio is planned for a future release. VS 2005 and 2008 can coexist on the same computer, but care must be taken to not open an existing VS 2005 project in VS 2008 and convert it since the project file conversion is one way and cannot be reverted. The Conversion Wizard prompts you to create a backup before converting the project and this is recommended for any project.|