Release of Service Fabric SDK 2.1.150 and Runtime 5.1.150


Today, we are releasing Service Fabric SDK v2.1.150. This release includes a number of new features, along with a set of important bug fixes. You can get the updated SDK from the links below:

We are also releasing an update to the preview of the standalone installer for Windows Server, based on runtime v5.1.150.

Highlights

ASP.NET Core 1.0 RC2 template

We’ve added an ASP.NET Core project template so that you can easily include a web app or web service in your Service Fabric application. To learn how you can add an ASP.NET frontend to your application, take a look at this tutorial.

Azure Active Directory for client authentication

You can now use Azure Active Directory to authenticate clients to your cluster management endpoint, as an alternative to using client certificates. Follow this tutorial to get started.

Build Service Fabric applications without installing the SDK or Visual Studio

Many of you asked for a way to perform automated builds of Service Fabric applications without requiring the SDK and Visual Studio to be installed. With this release, we’ve encapsulated all build artifacts into a standalone NuGet package that can travel with your project so that all you need is MSBuild. This enables the use of Visual Studio Team Services (VSTS) hosted build agents. To learn how to set up continuous integration with Service Fabric, follow this tutorial.

Package guest executables in Visual Studio

Service Fabric enables the packaging and running of arbitrary executables as services, providing the availability and scalability benefits of the platform to software written in any language or framework. These services are referred to as guest executables and with this release, it’s much easier to work with them in Visual Studio.  Simply tell VS where it can find your executable and how you want it started and it will take care of the rest, including creating a service manifest and updating the application manifest. You can learn more about guest executables here.

RunAsync cancellation delays generate health warnings

When the cancellation token provided in RunAsync is signaled, you are expected to shut down quickly and gracefully to enable the platform to complete the operation in progress. With this release, long delays in responding to cancellation will automatically generate a health warning to help diagnose issues that arise as a result.

Fix for blue screens/crashes that occurred when sleeping/waking onebox machines

Several customers reported blue screens when coming out of sleep on their development machines. This has been resolved.

For a list of everything in this release, please see the detailed release notes.

Other notes

  • We have completed the rollout of the Service Fabric runtime upgrade (v5.1.150) to Azure clusters worldwide. If your cluster was not upgraded, it likely means that it was not in a healthy state or that it went into an unhealthy state during the upgrade and was rolled back. You can learn more about the upgrade process here.
  • Starting with this release, we will maintain at least the last two minor versions of the Service Fabric SDK in the Web Platform Installer feed. Simply search WebPI for “service fabric” to see all available releases.

Questions, issues and feedback

As always, we’re watching out for your feedback and bug reports. See here for a list of places you can find us.

Cheers,

The Service Fabric Team


Comments (26)

  1. Khaled Hikmat says:

    Great stuff. Is .NET 4.6x now supported on the SF clusters?

    1. .NET 4.6.x is supported on Service Fabric. However, it is not present by default on the VMs that are provisioned for clusters in Azure. We are working on getting it added but for now, you need to install it as a custom VM extension

      1. Jan Burian says:

        Any idea when .NET 4.6 will be present by default?

      2. Nick says:

        I am also excited to see support for 4.6.x in Azure VM’s by default.

  2. Weston Weems says:

    After downloading platform installer to upgrade the tools for vs.ent 2015, the installer fails saying i followed a bad link

    1. The deep link was temporarily broken. Please try again.

  3. Awesome stuff. Can we now add and remove individual nodes for On-Prem? That has been promised for over a month, but it is not on your notes.

    1. Are you going to reply to this?

    2. Oliver Tomlinson says:

      Yes you can. Download the and extract the 5.1 runtime and you will see there is a AddNode.ps1 and RemoveNode.ps1

  4. SondreB says:

    When launching the ServiceFabricSDK.exe, it will launch Web Platform Installer with an error message that it can’t find the product. Then when you search for “Service Fabric”, there are only “Microsoft Azure Service Fabric SDK – 2.1.150 (VS2015)” and “15” Preview available. These require Visual Studio to be installed. That means it’s currently not possible to find and install the SDK and Runtime only. I need the SDK to be able to run publish of new application directly from the Azure cluster, which we have to do until the deployment timeout issue is fixed. Could anyone please supply the direct download link for “Runtime and SDK only (no tools)”?

    1. Yes, there was a bug in the deep link and the core SDK is not discoverable from within WebPI. The link should be fixed now and we will make the core SDK visible in WebPI.

  5. JohnnyC says:

    Has anyone been able to install ‘Runtime, SDK, and tools for Visual Studio 2015’?
    I’ve downloaded it multiple times since the 13th, each time Web Platform Installer fails with error ‘couldn’t find the product you tried to install….’

    1. Please try again. There was an issue with the link that should be fixed now.

  6. Adam says:

    Hi, after installing most recent version of SDK my VSTS CI build has broken. Has anyone observed such issue? Details: http://stackoverflow.com/questions/37858616/continous-integration-on-vsts-broken-after-installing-most-recent-service-fabric

  7. Max says:

    Hi, when I add a new ASP.NET Core project with the “Web Application” template to my Service Fabric application project I get immediately these dependency errors:

    The dependency Microsoft.Extensions.Options 1.0.0 in project Web1 does not support framework .NETFramework, Version=v4.5.2
    The dependency System.Runtime 1.0.0 in project Web1 does not support framework .NETFramework, Version=v4.5.2

    How can I resolve this?

  8. Håkon says:

    Hello when I try to scale my on-premise cluster with the recently added AddNode.ps1 script I get the following errormessage:

    ExtractInstallerService failed to extract C:\Users\fabadmin.FABRIC\AppData\Local\Temp\2\mp0ctn3z.u44\FabricInstaller
    ice.Code.
    AddNode Exception -1: System.IO.DirectoryNotFoundException: ExtractInstallerService failed to extract C:\Users\fabad
    FABRIC\AppData\Local\Temp\2\mp0ctn3z.u44\FabricInstallerService.Code.
    at System.Fabric.ConfigureNodeUtility.ExtractInstallerService(String cabPath, String pathToExtract)
    at System.Fabric.ConfigureNodeUtility.c__DisplayClass2.b__0()
    at System.Threading.Tasks.Task.Execute()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Fabric.DeploymentManager.d__2b.MoveNext()

    1. Max says:

      I can not find any “AddNode.ps1” script…

  9. Tony says:

    Thank you for enabling SF on the hosted build servers!
    Is there any info on integrating with Release Management and Application Insight?

  10. Daniels Danilins says:

    FabricTypeHost.exe crashed always on Windows 7. But runs on Windows 10.
    The problem is ese.dll. It looks for AddVectoredExceptionHandler function in api-ms-win-core-debug-l1-1-0.dll. But does not find it, because it does not exists there. Then it unloads the library with FreeLibrary() and crashes there.
    Is there any place where I could create an issue?

  11. Richard Calderón says:

    I can´t find WcfCommunicationListener anywhere,

    1. Richard Calderón says:

      My bad, I had search for it under nugget packages.

  12. Simon Cromarty says:

    Every time I try to download the Visual Studio SDK and tools I get an error: “Server Error in ‘/web’ Application.”
    Looks like there’s a problem with the download link.
    Is this just me or is anyone else having similar problems?

    1. This is an intermittent issue we’re seeing with the WebPlatformInstaller links. We are looking into it. In the interim, the latest release notes include direct download center links.

  13. ravi says:

    My one node out of 3 got corrupted somehow. then i tired to remoe that node and add but getting belwo error while add node with addnope.ps1
    Can anyone help me what i am missing
    Source package path invalid: MicrosoftAzureServiceFabric.cab.
    AddNode Exception -1: System.IO.FileNotFoundException: Source package path invalid: MicrosoftAzureServiceFabric.cab.
    at System.Fabric.ConfigureNodeUtility.c__DisplayClass2.b__0()
    at System.Threading.Tasks.Task.Execute()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Fabric.DeploymentManager.d__2a.MoveNext()
    AddNode completed.

    1. ravi says:

      i am getting this error with addnode.ps1

      Configuring nodes.
      ExtractInstallerService failed to extract C:\Users\rbhusha\AppData\Local\Temp\2\rcpyyrjd.mpg\FabricInstallerService.Code
      .
      AddNode Exception -1: System.IO.DirectoryNotFoundException: ExtractInstallerService failed to extract C:\Users\rbhusha\A
      ppData\Local\Temp\2\rcpyyrjd.mpg\FabricInstallerService.Code.
      at System.Fabric.ConfigureNodeUtility.ExtractInstallerService(String cabPath, String pathToExtract)
      at System.Fabric.ConfigureNodeUtility.c__DisplayClass2.b__0()
      at System.Threading.Tasks.Task.Execute()
      — End of stack trace from previous location where exception was thrown —
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at System.Fabric.DeploymentManager.d__2a.MoveNext()
      AddNode completed.

      Above error is coming with “add-servicefabricnode” cmdlet

Skip to main content