Apr 5, 2012
  2908
(5 votes)

Similarity between EPiServer CMS and WSS

Having worked on EPiServer CMS and WSS I tend to compare both the technology. Both the CMS are made on .net so it is natural that they share similar feature. One of them is a VPP.

.Net framework 2.0 introduced a class called Virtual Path provider.

(http://msdn.microsoft.com/en-us/library/system.web.hosting.virtualpathprovider(v=vs.80).aspx)

 

In EPiServer CMS it is used to hold the static files. The files are saved within the system folder and a virtual file system is created using VPP class. It acts as an interface between base file system and the CMS users.

In WSS VPP class is used for URL rewriting. WSS has its own version http application/http modules where it uses the VPP class.

 

Similarly there are many more features shared between EPi Server and WSS.

Apr 05, 2012

Comments

Please login to comment.
Latest blogs
A Synonyms Manager for Optimizely Graph

If you’re using Optimizely Graph for search, synonyms are one of the simplest ways to improve relevance without touching content. But they’re also...

Pär Wissmark | Mar 17, 2026 |

Building a Better Link Validation Report in Optimizely CMS 12

Broken links frustrate visitors and damage SEO. I have made a custom broken links report, that makes it easier to work broken links than the built-...

Henning Sjørbotten | Mar 17, 2026 |

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

Discover what's new in Jhoose Security Module 3.0, including site-level security configuration for multi-site Optimizely solutions with global...

Andrew Markham | Mar 15, 2026 |

Running 64 Sites on Headless Optimizely CMS with GraphQL

64 websites. Live. Running on headless Optimizely with GraphQL. We just wrapped a major rollout for our Rockwool Digital Experience Platform  and t...

Piotr | Mar 14, 2026