32-bit and 64-bit support

32-bit/64-bit Compatibility As of K2 blackpearl 4.6, the following components and platforms are supported: Server Components (64-bit support only): K2 Server, K2 Databases, K2 for SharePoint, K2 Runtime Web Services, K2 Workspace, K2 for Reporting Services Client Components (32-bit and 64-bit support): K2 Studio, K2 for Visual Studio, K2 Documentation

K2 runs in full 64-bit mode, meaning that it is a true 64-bit application and therefore does not have the 2 GB restriction that 32-bit applications have when running the 64-bit version.
 
95% of the code is compiled in a MSIL and will run in 32-bit and 64-bit depending on the environment hosting K2. The other 5% gets compiled to target a specific instruction set (x86 or x64) and is mostly the unmanaged components like the host server core and services. With installation, the installer detects if the environment is 64-bit or 32-bit and will install the correct components. When installing on a 64-bit environment, the 32-bit components will be installed as well. It is clearly visible in the Global Assembly Cache. These components are required by applications like “Microsoft Visual Studio” that is 32-bit application only and will execute under the WOW (Windows on Windows) emulated process. These applications cannot make use of the 64-bit components and therefore the 32-bit components are required.

The platform (e.g., 32-bit or 64-bit) must be identical for all servers that are Network Load Balanced participating in a K2 blackpearl Role. The K2 installer will install the appropriate 32-bit components when K2 Designer for Visual Studio are installed.

The K2 blackpearl 64-bit installer can be deployed in a number of scenarios. As an overview, 32-bit and 64-bit components can be configured in an environment and function as a whole to provide a fully deployed system.

The table below describes the various supported communication topologies between 32-bit and 64-bit components: