Release of SDK 2.5.216 and Runtime 5.5.216 for Windows


We're pleased to announce that version 2.5.216 of the Service Fabric SDK is now available, along with the 5.5.216 runtime that rolled out to Azure clusters world-wide over the last week.

This release contains some exciting new features and lots of other improvements. Read more about this release on the Azure blog, or go straight to the detailed release notes.

Cheers

The Service Fabric Team


Comments (5)

  1. Jamie says:

    How do I run an application in Refresh Application Debug Mode? I only see “Auto Upgrade”, “Remove Application”, and “Keep Application” in the application debug mode drop down for the project. I am using VS2015 and have confirmed that the latest SDK and tools are installed. Thanks in advance.

    1. Sounds like you’re looking in the right place. Can you double check that you have Microsoft Azure Service Fabric Tools for Visual Studio 2015 v1.5.50311.1 installed under Programs and Features?

  2. Sascha says:

    The tools for VS 2015 are updated to 1.5 but VS 2017 remains on 1.4. There is not update to be found. Am i missing something or are the tools for VS 2017 not released yet?

    1. You’re not missing anything, the 1.5 tooling for VS2017 shipped a few days later. You should be able to get the new tooling for VS 2017 now by updating your installation of VS 2017 to 2017.1

  3. Can I make a few suggestions regarding updating? 1) There seems to be a problem when updating the SF MSBuild component. The latest went from 1.4.0 to 1.5.0. The .sfproj files were not automatically changed and were referring to the 1.4.0 version which resulted in some odd errors. 2) Is it possible to save the SDK in a versioned folder? This impacts TFS builders in that one builder cannot build two different versions of SF code. It takes time to update several hundred projects and having the build/deploy system able to do double duty would be nice. If not possible then please add a version.txt file that contains the SF version that the SDK applies to. Builders/Release agents should be able to use NuGet to retrieve all required deployment scripts – not have to have the SDK installed. 3) A final peeve is that when removing objects from the library, please document what the replacement is. For example, we are using Azure KeyVault and the KeyVaultClientException no longer exists. It took debugging to determine the exception that is totally new.

Skip to main content