Quan Mai
Oct 7, 2015
  3040
(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

Please login to comment.
Latest blogs
A First Look at Optimizely Remote MCP Server for Experimentation

Optimizely just released a Remote MCP Server for Experimentation and I've been trying it out to see what it can do. If you don't know, MCP (Model...

Jacob Pretorius | May 1, 2026

Promoted and Certified

What a busy week

Andy Blyth | May 1, 2026 |

Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026