Symptoms
Visual Studio Warning
Diagnoses
When you have recently upgraded to 4.6.11 and have been attempting to make changes to an existing custom solution using Visual Studio 2010.
The products forming this solution are:-
Visual Studio 2010 SP1
K2 Blackpearl 4.6.11 (Assemblies are now Version 4)
SharePoint 2010 SP2 - Target .Net Framework 3.5
Compile complete -- 0 errors, 1 warnings
C:WindowsMicrosoft.NETFrameworkv4.0.30319Microsoft.Common.targets(1605,5): warning MSB3270: 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, processorArchitecture=x86", "AMD64". 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.
C:WindowsMicrosoft.NETFrameworkv4.0.30319Microsoft.Common.targets(1605,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "SourceCode.Workflow.Client, Version=4.0.0.0, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d, processorArchitecture=x86", "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.
What could be the cause of this issue?
Resolution
This is a warning that can be ignored. This normally occurs if you installed .net 4 or 4.5. This is mentioned in the article below as well:
http://blog.andypotts.com/2012/08/installing-net-45-or-vsnet-2012-causes.html
