Apr 5, 2012
visibility 3115
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
Two more database surprises when upgrading from CMS 11 to CMS 13

Back in June I wrote about four database surprises when upgrading from CMS 11 to CMS 13 ( old post ). Here are two more, found on another CMS 11...

Per Nergård (MVP) | Sep 8, 2026

WebMCP providing understandable actions to agents in Optimizely

WebMCP is coming to Optimizely: a strategic view for CMS and Commerce teams At Opticon 2026 in New York, Alex Atzberger framed Optimizely's strateg...

Scott Reed | Sep 8, 2026

The Optimizely SaaS CMS Administrator Certification: More Than an Admin Exam

When I started preparing for the Optimizely SaaS CMS Administrator Certification, I expected most of the material to focus on administrative work:...

Augusto Davalos | Sep 8, 2026

Two Machines, One Memory

How to keep a Claude Code memory store in lockstep across two machines, using nothing but git and two hooks. We've been running Claude Code against...

KennyG | Sep 7, 2026