Apr 5, 2012
  2964
(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
Building a Custom RAG for Optimizely Opal

How to design a standalone RAG service for documents that don't belong in Optimizely One, and expose it to Opal and other AI tools without coupling...

Michał Mitas | May 14, 2026 |

Semantic Search - Deep Dive

Deep dive into semantic search with Optimizely Graph

Michał Mitas | May 14, 2026 |

Building a Custom RAG for Optimizely Opal

Opal's built-in knowledge is limited to content inside Optimizely One. Here's how to design a custom RAG service for documents that live outside th...

Michał Mitas | May 14, 2026 |

The Fragment Conundrum

Explore the challenges and opportunities of working with Optimizely SaaS, GraphQL fragments, and headless CMS architectures. Learn practical...

Andy Blyth | May 13, 2026 |