Dan Matthews
Jun 1, 2010
  5120
(1 votes)

Mixing 32-bit and 64-bit development

I came across a weird little problem with a mixed 32-bit and 64-bit Windows 7 development team. Because EPiServer installs by default into Program Files (x86) on 64-bit, the virtual paths for the CMS UI point to different physical folders in the episerver.config, compared to the 32-bit installations which don’t have the (x86) version of the Program Files folder. If you try and share the config file without realising this, either the 32-bit or 64-bit machines are going to give you a 404 resource not found when trying to access edit or admin mode.

You could not put the file into source control I suppose, but that’s a bit messy. Easiest way I found is to use the 32-bit style of Program Files folder in the episerver.config, then create a symbolic link on the 64-bit Program Files folder.

To do that on the 64-bit machines:

  1. open an administrator command prompt
  2. cd “Program Files”
  3. mklink /D EPiServer “C:\Program Files (x86)\EPiServer”

That should be sorted, and all should run perfectly with the same episerver.config!

Jun 01, 2010

Comments

Please login to comment.
Latest blogs
Running the Optimizely CMS 13 Alloy Site on macOS with Docker

In my first Apple Silicon post and the 2025 revisit I covered running an Optimizely Foundation site on an M1/ARM Mac. This time I wanted to try...

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

Stott Security v7 for Optimizely CMS 13

Stott Security version 7 is now available for  Optimizely PaaS CMS 13 , introducing support for configuring security headers by both  application...

Mark Stott | Apr 9, 2026

Optimizely CMS 13 and errors when creating pages after upgrade

After upgrading to Optimizely CMS 13, I ran into issues creating pages and deleting media. The fix was easy!

Tomas Hensrud Gulla | Apr 9, 2026 |

Optimizely CMS 13 and the new login/admin/edit URL

What happened to /episerver/cms after upgrading to Optimizely CMS 13?

Tomas Hensrud Gulla | Apr 8, 2026 |

Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |