Per Bjurström
Mar 6, 2017
visibility 5769
star star star star star
(10 votes)

Support for Visual Studio 2017

A new version of the Episerver Visual Studio extension with support for Visual Studio 2017 is now available on the Visual Studio Marketplace. We support all editions from Community to Enterprise. Visual Studio 2017 will be available for download on March 7th.

The best way to install it is using the "Extensions and updates" menu inside Visual Studio.

Image InstallVSExtension.PNG

What changed

This new version contains the latest releases of the CMS NuGet packages, we plan to have another version released in the coming weeks with the latest version of the Find packages as well.

Visual Studio 2017 requires add-ons to adhere to new rules and a packaging format to support the minimal footprint of Visual Studio 2017. So there are a lot of under-the-hood changes in this release.

There is also full support for Visual Studio 2015 ofcourse. Support for Visual Studio 2012 and 2013 has been dropped for this version, but will make the old version downloadable stand-alone.

The page on the Visual Studio Marketplace contains more details. Try it out and let us know if you find any issues.

Mar 06, 2017

Comments

Mar 6, 2017 06:03 PM

Would be nice if Visual Studio Extension could be extended so that developers can choose which version of EPiServer they want to install :)

Could be handy when testing if an add-on works in previous versions of Epi.

per
per Mar 7, 2017 04:23 PM

Yes that would be nice, I have a git repo with different versions instead, that makes it fast to switch between versions using tags.

valdis
valdis Mar 13, 2017 10:24 PM

Per, are you considering to open this up for community to contribute?

per
per Mar 14, 2017 09:29 AM

Valdis, not on the backlog but is a good idea

Mar 22, 2017 06:11 PM

Per, are there any plans to add Episerver Commerce features? (This could be related to Valdis' comment)

per
per Mar 23, 2017 09:13 AM

Petter, Commerce team is looking into it.

bikram khanal
bikram khanal Jun 13, 2017 05:34 PM


Sorry to raise a question in this chain. I didn't find any related chain so posted my question here.

We have mvc projects and we load some of the images for the landing pages from epi-server using global assets folder..
The images are loaded in the html during the run time and are stored with unique identifier in
sql db. Making changes on the web-config works fine for the local but while deploying it is being
overriden by different value.

I tried most of the way instructed in the blog as well.

Can you guide me to find a way to cache these images?

Thanks a lot.

error Please login to comment.
Latest blogs
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |