Quan Mai
Oct 7, 2015
visibility 3118
star star star star star star
(3 votes)

Important note for installing EPiServer.Commerce.Azure 9 nuget package.

In the next major version of Commerce, we added a new assembly to EPiServer.Commerce.Azure. We got feedback from QA team during testing that the new assembly was not copied to bin folder, causing some issues.

We have investigated the issue and at first everything looked normal. The project had the reference to the assembly, the path was correct and Copy Local was set to true. But when we rebuilt the project, only new assembly was not copied to bin folder.

After some digging, we found that:

- The problem only happens on Visual Studio 2012/2013. We have no issue with VS2015.

- If we close the project, then open it again, then rebuild then the problem is fixed.

Our assumption is that Visual Studio 2012/2013 has some issue with caching list of referenced assemblies. This was fixed on VS2015.

With the issue of Nuget 2.x on Visual Studio 2012/2013 (Issues with NuGet package updates), we now have more reasons to recommend you to use Visual Studio 2015.

Oct 07, 2015

Comments

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |