Symptoms
There is a workflow (*.kprx) within a solution file (*.sln) which fails to be deployed from Visual Studio 2010 with the following warning:
Warning: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "SourceCode.HostClientAPI, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
In Configuration Manager (Build > Configuration Manager) Platform is set to "Any CPU". Previously this solution/workflow used to deploy without any issues.
Diagnoses
The fact that in Configuration Manager (Build > Configuration Manager) Platform setting is set to "Any CPU" could be the cause of the warning mentioned above (there is certain issues around this warning and sometimes you need explicitly set x86 or x64 instead of Any CPU to get rid of this warning). But this warning does not explain deployment failing with no errors being returned.
It could be the case that one particular workflow within the solution can be deployed only with disabled check box ’Create Workflow Reporting SmartObjects’.
For details on this setting please refer to respective section of K2 documentation:
https://www.k2.com/onlinehelp/k2blackpearl/userguide/4.6.7/webframe.html_so_create_workflow_reporting_smartobjects.html
The "Create Workflow Reporting SmartObjects" option will create a smartobject for the process that would allow you get process instances data that was created by the process. With this option selected, the process smartobject will be in the Workflow Reports smartobject category. This smartobject is mainly use for reporting purposes, it'll return process data field and process xml field.
Resolution
Try to deploy affected process with disabled check box ’Create Workflow Reporting SmartObjects’ or recreate this process from scratch.
