Upgrading EPiServer Commerce R3 to EPiServer 7.5 – upgrade script errors

Here is a little summary of problems and solutions with the Commerce upgrade script.

Run Deployment Center as administrator. The upgrade script upgrades both EPiServer 7.0 and EPiServer Commerce R3 to EPiServer CMS and Commerce 7.5. So the first step is to choose: “Upgrade EPiServer Commerce”

Next step choose the CMS 7 “Commerce enabled” www site to upgrade. (Not the Commerce manager site)

This is the running script:
“C:\Program Files (x86)\EPiServer\CMS\7.5.394.2\Install\Modules\EPiServer Commerce 7.5.394.2\Install\Upgrade EPiServer Commerce.ps1”

This is where you could inspect the log if it fails: (latest modified file)
C:\Program Files (x86)\EPiServer\Shared\Install\Logs


Could not find file ‘C:\sites\MySite.Web\b\web.config’1.

Solution: Set  <appSettings> key “CommerceManagerApplicationName” to the Commerce Managers current IIS ApplicationPool name.


Line 418 fails: Could not find file ‘C:\commerce\MySite.CommerceManager.Web\b\web.config’.

Solution: this line:  $commerceManagerPath = $commerceManagerBinPath.trimEnd(“Bin”)
Is hardcoded in the ps1 script. Replace the appsetting “CommerceManagerBinPath” in wwwroot web.config file “bin” in the path to “Bin”. E.g:


“Could not find Tools.zip”

Copy Tools.zip from wwwroot\MediachaseECF\* (from a functioning, or demo, epi7 commerce r3 site) to upgradeprojects\wwwroot\MediachaseECF\*.

This file also seems to be deleted after every upgrade attempt.
Download here: Commerce_Tools.zip_for_r3_and_75

Cannot find package “EPiServer.Business.Commerce.AddOns.Manager” in local repository.

–  In your wwwroot\modulesbin folder there should be a EPiServer.Commerce.AddOns.Manager.dll file, the EPiServer.Business.Commerce.AddOns.Manager.dll is EPiServer Commerce R3 specific and should be deleted.

Remove-Item : Cannot find path ‘C:\commerce\MySite.CommerceManager.Web\bin\Mediachase.Cms.Website.dll’ because it does not exist.

At C:\Program Files (x86)\EPiServer\CMS\7.5.394.2\Install\Modules\EPiServer Commerce 7.5.394.2\Install\Upgrade EPiServer Commerce.ps1:378 char:3

Solution: copy the Mediachase.Cms.Website.dll from C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\Install\Modules\EPiServer Commerce\ECF\Data\ConsoleSite\bin to manager bin folder.

Speeding up ASP.NET development environment with a memory ram disk

The basics for these tips are that you are willing to use some of your computer memory to speed things up.

The concept is to use a RAM disk for temporary files storage to speed up the development environment. I am currently using 512 memory on my 8gb Windows 8 pc for the RAM disk.

The tips originates from:

Step 1. Install Ram disk (free software):
Run ImDisk Ram Disk Configuration.
Set drive to q: and 512mb RAM disk on my 8 gb memory pc, enable “Launch at Windows Startup”.


Above: here the drive size is set to 512mb. Its changeable, its a “temp” drive. Its non persistant everything gets wiped upon system restart.

Step 2. Set asp net temp folders pointed to RAM disk:
(from http://blog.lavablast.com/post/2010/12/01/Slash-your-ASPNET-compileload-time.aspx)
“To speed up the first load time, you can tell IIS to store its temporary files on your RAM disk (or fastest disk) by changing the following setting in your web.config files:

You can either change your project files directly, or, if you’ve lazy and have numerous applications running on your development machine (like I do), update the system-wide web.config files. Note that you need to update this for each runtime version of the Framework and, if running a 64-bit machine, for both Framework and Framework64. On my machine, I needed to modify the following files:

1: C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\Web.config
2: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\Web.config
3: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\Web.config
4: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\Web.config

Step 3. Chrome cache pointed to RAM disk:
If you use Chrome as development browser this tip helps you point out the custom cache folder and set a size.

Shortcut target value (pointed to q: drive and 100mb cache) :

Regedit value:
Change HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command in Windows registry to


The results
It feels like my computer is “snappier” and faster when surfing in Chrome. But I am not really sure if the time to render first page after build is any faster? It still takes about 1 minute after rebuild of entire solution.

More tweaks

Tell antivirus (for me its just windows defender) to exclude q: folder from scanning. You could also add your base projects folder and Visual Studio folders;
C:\Program Files (x86)\Microsoft Visual Studio 11.0
C:\Program Files (x86)\Microsoft Visual Studio 12.0

Excluded process:

Create a bat file for starting Visual Studio to enforce Visual Studio temp files to q:

Bat and shortcut file for download:
Visual Studio 2013.zip

Set ReSharper temp files to use system temp as well:

Not sure if this speeds things up: (just another temp folder used by IIS):