World is now on Opti ID! Learn more

smithsson68@gmail.com
Sep 1, 2011
  7150
(0 votes)

EPiServer CMS Visual Studio Integration Extensions

EPiServer CMS 6 R2 ships with a Visual Studio Integration package that you can optionally install from the zip download found here.

Once this is installed, you get not only a new EPiServer Project type but also EPiServer components that can be created using the Add New Item menu:

image

 

Unfortunately, due to time constraints, this hasn’t been kept inline with the juicy new features added in CMS 6 R1 and R2.

With that said, I have taken an old VS Integration extension package that Fredrik Tjärnberg released a while back and added some of those juicy bits from CMS 6 R1 and R2.

After you have installed the extension, in addition to the 4 EPiServer items already available, you get 3 new ones: Dynamic Content, Online Center Gadget and Visitor Group Criterion:

image

 

All of the new items come with an array of options to chose from when you create one.

For Dynamic Content, you chose what type of component to create to render the content along with the option to create a custom Editor:

image

 

For an Online Center Gadget, you can chose to optionally create a model class and a JQuery based Javascript file:

image

 

And last but not least, for a Visitor Group Criterion, you get options to create a model class, a custom Editor and a Dojo based Javascript file (for the custom Editor):

image

 

Whilst VS Integration may not feel mission critical for seasoned EPiServer developers, it can be very useful for new developers. I also think that some of the new options could be useful for all when creating components with custom editors and javascript files.

The VS Integration Extension installer can be found here. Both Visual Studio 2008 and 2010 are supported including Visual Web Developer and VS Professional / Team Edition.

Whilst this is not an official EPiServer release I intend to fix bugs and add new features so let me know if you have any issues or ideas.

Happy coding!

Sep 01, 2011

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |