Try our conversational search powered by Generative AI!

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


Please login to comment.
Latest blogs
Optimizely Web... 6 Game Changing Features in 2024

If you are interested in learning about what's new within Optimizely Web, you are in the right place. Carry on reading to learn about the 6 greates...

Jon Jones | Mar 3, 2024 | Syndicated blog

Headless forms reloaded (beta)

Forms is used on the vast majority of CMS installations. But using Forms in a headless setup is a bit of pain since the rendering pipeline is based...

MartinOttosen | Mar 1, 2024

Uploading blobs to Optimizely DXP via PowerShell

We had a client moving from an On-Prem v11 Optimizely instance to DXP v12 and we had a lot of blobs (over 40 GB) needing uploading to DXP as a part...

Nick Hamlin | Mar 1, 2024 | Syndicated blog

DbLocalizationProvider v8.0 Released

I’m pleased to announce that Localization Provider v8.0 is finally out.

valdis | Feb 28, 2024 | Syndicated blog