Visual Studio 2017 and Service Fabric tools


As you’ve probably already heard, Visual Studio 2017 released last week. Some of you might have already been trying out Visual Studio 2017, and noticed that Service Fabric Tools are now part of the Visual Studio installation.

This blog post is to give you a quick overview of some of the changes in Visual Studio 2017 getting set-up for developing Service Fabric applications.

What’s New in Visual Studio 2017

Visual Studio 2017 brings an entire range of new features to your overall developer experience. See here to get a good overview of these: https://www.visualstudio.com/vs/whatsnew/

With Visual Studio 2017, Service Fabric Tools are installed as part of the Azure Workload. This gives you a straightforward way of getting the tools you need for developing Service Fabric applications.

To get the full developer experience, you need to install the SDK through Web Platform Installer (WebPI). See here for details: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started#install-the-sdk-and-tools.

.NET Core

.NET Core tools for Visual Studio 2017 is based on a new project system, which is not compatible with Visual Studio 2015. If you have created a .NET Core project in Visual Studio 2015 (xproj) and you want to start using Visual Studio 2017, you will be guided through a one-way migration, migrating the project type to the new .NET Core project system. This of course impacts Service Fabric services written using .NET Core, as these are no longer compatible with Visual Studio 2015. See her for more info about .NET Core tools: https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-to-project-json/.

Supporting both Visual Studio 2015 and Visual Studio 2017

All the features you need for developing Service Fabric applications are the same across Visual Studio 2015 and Visual Studio 2017. Our plan is to keep continuing supporting both versions of Visual Studio, and to ensure the ability to use both versions across solutions. The only exception is the support for .NET Core project, which is described above.

Keeping up to date

Going forward we will release the updated Service Fabric Tools as part of Visual Studio 2017 updates. This way you do not have to worry about getting the latest and greatest tool set for developing Service Fabric.

To stay current on runtime and SDK, you will still need to update these via the Web Platform Installer (WebPI). Runtime and SDK releases are announced on this blog.

For Visual Studio 2015, Service Fabric Tools are still only available via Web Platform Installer (WebPI).

Here is a quick comparison of VS 2017 and 2015:

  VS 2017 VS 2015
SF Tools Built-in to Visual Studios Azure Workload Install through Web PI
SF Runtime and SDK Install through Web PI Install through Web PI
.NET Core .csproj (not backward-compatible) .xproj (one-way forward migration)
Service Fabric supported Yes Yes

Comments (3)

  1. Gergely Kalapos says:

    This part is extremly confusing:

    “With Visual Studio 2017, Service Fabric Tools are installed as part of the Azure Workload. This gives you a straightforward way of getting the tools you need for developing Service Fabric applications.

    To get the full developer experience, you need to install the SDK through Web Platform Installer (WebPI). ”

    So.. is it installed with the Azure workload, or not? What is “full developer experience”. I really don’t know based on this, whether I need to install the SDK after I installed the Azure workload. I’m more confused after reading this doc..

    1. Hi Gregely, Sorry for the long wait, but wanted to address your question here for others as well. For Visual Studio 2017, you need to install the SDK package from WebPI in addition to the Azure Workload. What is installed with the Azure Workload is the Visual Studio tools for Service Fabric, as pointed out in the table above.

  2. devo says:

    Visual studio community includes service fabric tools?

Skip to main content