Optimizely
Apr 12, 2014
visibility 3683
star star star star star
(0 votes)

Running Commerce Manager R2 SP2 in a .NET 4.0 AppPool

This is my first blog post, but I’ll keep this short and sweet.

Since we don’t have any docs showing how to run Commerce Manager R2 SP2 in a .NET 4 appPool, here’s a way to do it for those running this older version of Commerce.

1. Open the B2CSampleSite.sln in Commerce Manager site folder in Visual Studio.

2. Look at the Properties of the project and then change target framework from 3.5 to 4.0.

3. Build the project.

4. Go to the Commerce Manager web.config and look at this section:

<runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <dependentAssembly>

        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>

        <bindingRedirect oldVersion="1.0.0.0-4.0.0.0" newVersion="4.0.0.0"/>

      </dependentAssembly>

      <dependentAssembly>

        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>

        <bindingRedirect oldVersion="1.0.0.0-3.5.0.0" newVersion="3.5.0.0"/>

      </dependentAssembly>

    </assemblyBinding>

  </runtime>

5. Change System.Web.Extensions from oldVersion=”1.0.0.0-3.5.0.0” to oldVersion=“1.0.0.0-4.0.0.0’'” and newVersion=”3.5.0.0” to newVersion=”4.0.0.0”

6. Save the web.config and access Commerce Manager.

That should do it!

Apr 12, 2014

Comments

Jeff Valdez
Jeff Valdez Apr 15, 2014 07:54 PM

Nice and easy! :)

error Please login to comment.
Latest blogs
Exploring Cached Templates and Cursor Pagination in the Optimizely Graph C# SDK

While experimenting with the  Optimizely Graph C# SDK (13.3.0) in my local Optimizely CMS 13 Alloy project, I came across two interesting findings:...

Mardy | Oct 19, 2026

EPiServer.ImageLibrary.ImageSharp 2.0.7 delisted from NuGet feed

We have delisted version 2.0.7 of the EPiServer.ImageLibrary.ImageSharp package from the NuGet feed due to a packaging issue. This version was...

Phu Nguyen | Oct 19, 2026

Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026