Apr 5, 2012
visibility 3095
star star star star star
(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

error Please login to comment.
Latest blogs
Copies vs. Connections: Modeling Content Areas for Multilingual Success

Starting With the Simple Question Most multilingual content modeling conversations start with a deceptively simple question from a client: "If we s...

Vipin Banka | Aug 23, 2026

Content Transfer coming to Optimizely SaaS CMS

Back in June I released Content Transfer on the Optimizely nuget feed – today I’m releasing version 1.0 , because we’ve had it running out in the...

Matt Pallatt | Aug 23, 2026

Improving Optimizely Product Information in LLM Tools

Tools like Claude Code can be great for working with Optimizely CMS, but when they index outdated or incomplete information about developing a...

Nicholas Sideras | Aug 21, 2026 |

How to Get a Bacpac Out of DXP (And Never Do It By Hand Again)

Every Optimizely DXP project eventually runs into the same task: getting production data onto a local machine so you can actually troubleshoot...

KennyG | Aug 20, 2026