Per Bjurström
Mar 6, 2017
  5652
(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.

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |

Forcing Lowercase URLs in Optimizely CMS During Auto-Translation

Learn how to fix uppercase and punctuation issues in Optimizely CMS 12 URL segments caused by LanguageManager auto-translation using a custom...

Stuart | Apr 2, 2026 |

Stott Robots Handler v7 for Optimizely CMS 13

Stott Robots Handler version 7 is now available for  Optimizely PaaS CMS 13 . This is includes updates to support the switch from a Site based...

Mark Stott | Apr 2, 2026