A preview of Visual Studio 2017 Service Fabric Tools 2.0 is now available for download, packed with new .NET Core and Container tooling for Service Fabric application development. To start using the 2.0 preview tools, you'll need to install:
.NET Core 2.0 project templates
We recently released a 3.0-preview version of the Service Fabric SDK NuGet packages, built on .NET Standard 2.0, allowing you to build your services on either .NET Core 2.0 or .NET Framework 4.6.1. This update to the Service Fabric tooling for Visual Studio 2017 now has project templates that make it easy to create .NET Core 2.0 Reliable Services for stateless services, stateful services, and ASP.NET Core services, with Reliable Actor services coming soon in an upcoming release.
Containerize .NET Framework projects and run them on Service Fabric
Service Fabric is a general container orchestration platform, so we've made it incredibly easy to take any .NET Framework console application or ASP.NET application, and with a few clicks add it as a containerized service that runs on Service Fabric. To get started, right click on your project and select Add -> Docker Support for Service Fabric. This will create a Docker file in your project with a Windows 2016 Server Core base image, and a Service Fabric package root directory that you see with typical Service Fabric projects. If your project is part of a solution with an existing Service Fabric application, it will be added to that application automatically, otherwise a new Service Fabric application will be created automatically for you.
Debug containers running on Service Fabric
Not only can you easily containerize existing .NET projects and run them on Service Fabric with just a few clicks, but now you can also debug the code running inside the container instance as it runs on Service Fabric. Just hit F5 to get full debugging support within VS as your application runs in a container on Service Fabric! When it is time to publish your application to Azure we will prompt you for an Azure Container Registry to push your image to.
Refresh mode and one-node clusters are now the default
Refresh mode has been available as a preview feature but now it is on by default for new projects and no longer in preview. Using refresh mode increases the speed of your development cycle considerably! Refresh mode only works when you are debugging against a one-node cluster, so starting with our 2.0 tooling local dev clusters will default to one-node. If you want to take advantage of Refresh mode and faster F5 times but already have a local five-node dev cluster, switch over to a one-node cluster today!