Quan Mai
Oct 7, 2015
  2963
(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
Accelerating Optimizely CMS Upgrades with Intelligent Automation

Upgrading an Optimizely (formerly EPiServer) CMS solution has traditionally been a high-risk, resource-intensive endeavor. Transitioning from CMS 1...

Vaibhav | Apr 13, 2026

Optimizely CMS 13: The Evolution We’ve Earned

Tired of migration flashbacks? Optimizely CMS 13 is the evolution we’ve earned. Learn why the move to .NET 10 is easier and how AI-first...

Stuart | Apr 13, 2026 |

The Entra ID Surprise

How assumptions can lead to mysterious issues.

Damian Smutek | Apr 13, 2026 |

OptiPowerTools.Hangfire 2.0.0: CMS 13 Support and Sample Jobs

When I released OptiPowerTools.Hangfire back in March, it targeted Optimizely CMS 12. With CMS 13 now out and running on .NET 10, it was time to...

Stanisław Szołkowski | Apr 13, 2026 |