When you first start out developing for Commerce Server 2009 R2, you notice there are quite a large amount of code that they provide you to get started with.
Where To Start:
First you need to find the CommerceSharePointExtensibilityKit.zip file located at C:Program Files (x86)Microsoft Commerce Server 9.0Extensibility Kits
In this file you’ll see two Visual Studio solution files. I’m a fan of VS2010, so we’ll work with that, although it isn’t what these solutions were meant for.
Open the SharePointCommerce solution. Allow Visual Studio to do it’s conversion. You’ll now need to add the two other projects Common and SharePointCommon. They are located in the named directories from the base solution directory, you shouldn’t have any issues finding them.
Create your own SNK file:
Create a small console application with a SNK of your own choosing. Add signing to the project, then retrieve the PublicKeyToken for later use.
Replace the SNK file:
Copy your SNK file over the built in file MSSharedLibSN1024.snk, don’t delete rename, this will just create more work for you later.
Perform the following Search and Replace Operations within all files in the solution:
Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Version=18.104.22.168, Culture=neutral, PublicKeyToken=<YourKeyHere>
Culture=Neutral, Version=22.214.171.124, PublicKeyToken=31bf3856ad364e35
Culture=Neutral, Version=126.96.36.199, PublicKeyToken=<YourKeyHere>
Manually Edit this file:
CommerceSharePointExtensibilityKitSharePointCommonFeatureActivationCommerceFeatureActivationJobDefinition.cs Line: 1836
"Microsoft.CommerceServer.Interop, Version=188.8.131.52, Culture=neutral, PublicKeyToken=<YourKeyHere>"
"Microsoft.CommerceServer.Interop, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Now you will be able to build the entire solution, create the three WSP’s used by the custom installer, and use their handy tool to provision the site.