Jooeun Lee
Sep 9, 2015
(2 votes)

Asset Importer fix for EPiServer Commerce 8 and CMS 8

I recently helped a customer resolve this issue and will share the solution. The customer was developing on the latest versions of CMS and Commerce (i.e. version 8.X.Y). Breaking changes from CMS 7.X to CMS 8 prevented the Asset Importer from running in a set-up with Commerce and CMS 8.X.

In order to fix this, do the following:

  1. Update the Asset Importer project to match your Commerce site by installing NuGet packages.
  2. Get the fixes here.
  3. Run the tool as documented.

If you are interested in reading the details of the problem and the fix, go here.

If you need to solve this problem, I hope this helps. Please feel free to contact me with any questions/suggestions/bugs in EPiServer Expert Services by emailing me at or by leaving a comment below.

Sep 09, 2015


Please login to comment.
Latest blogs
Performance optimization – the hardcore series – part 2

Earlier we started a new series about performance optimization, here Performance optimization – the hardcore series – part 1 – Quan Mai’s blog...

Quan Mai | Oct 4, 2023 | Syndicated blog

Our first steps into local AI

After a consumer of tools like ChatGPT and CoPilot, we as developers like to dive deeper into it. How does it work? Where to start? Can I create my...

Chuhukon | Oct 4, 2023 | Syndicated blog

Update on .NET 8 support

With .NET 8 now in release candidate stage I want to share an update about our current thinking about .NET 8 support in Optimizely CMS and Customiz...

Magnus Rahl | Oct 3, 2023

Adding Block Specific JavaScript and CSS to the body and head of the page

A common requirement for CMS implementations includes the ability to embed third party content into a website as if it formed part of the website...

Mark Stott | Oct 3, 2023