In a previous post I introduced Virtual Template System for EPiServer. This post is a quick introduction on how to use the UI.
When you first open Virtual Template System by clicking Virtual Templates, then Edit you will be presented with a list of templates that are in the repository. As this is the first time you've used it the list will be empty. Clicking the "Show all templates (including those on disk)" option will list out all templates that are on disk, plus those already in the repository. By default it looks for cshtml, CSS and js within the application.
Quite simply Virtual Template System for EPiServer allows users to view and modify templates from the EPiServer UI. Why would you do this? The internet is a fast moving world and our customers and clients are demanding. They may not want to wait for a full release to update a template and shouldn't really need to if it's only for a couple of lines of mark up or CSS to be changed. Virtual Template System tries to help this issue by allowing users to make templates visible and editable from the EPiServer UI.
One of the most exciting features in EPiServer Commerce 7.5 (for me) is MetaClass and MetaField mapping from code to the Catalog system in EPiServer Commerce. In short this allows you to create/edit/access MetaClass and MetaFields in EPiServer Commerce 7.5 through code in the same way you can for any other content type in EPiServer.