Apr 5, 2012
visibility 3138
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
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |