{"id":24725,"date":"2018-05-27T19:50:00","date_gmt":"2018-05-27T19:50:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/premier_developer\/?p=24725"},"modified":"2019-02-14T20:18:06","modified_gmt":"2019-02-15T03:18:06","slug":"running-net-core-2-0-applications-in-a-linux-service-fabric-cluster-on-azure","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/running-net-core-2-0-applications-in-a-linux-service-fabric-cluster-on-azure\/","title":{"rendered":"Running .NET Core 2.0 applications in a Linux Service Fabric Cluster on Azure"},"content":{"rendered":"

In this post, Senior App. Dev. Managers Guru Satish Piduru<\/strong> and Mahendar Madhavaram<\/strong> explain how to deploy .NET Core 2.0 applications to a Linux Service Fabric Cluster.<\/p>\n

\n

\n

The support for running .NET Core 2.0 applications in Service Fabric Cluster (SFC) environment on Linux is in preview mode today and general availability in the coming months. Today, stateless Service Fabric applications are supported in .NET Core 2.0 without any issues. If you are using Microsoft Visual Studio 2017 to develop Service Fabric applications, you can publish the applications directly to Azure SFC running on Windows but if you want to publish the applications to Azure SFC running on Linux, you may run into some issues depending on the project type and template that you choose to create an application.<\/p>\n

In this post, we will demonstrate how to deploy .NET Core 2.0 applications to a Linux SFC using scripts until Visual Studio IDE provides this capability. <\/p>\n

Setup Local Service Fabric Cluster<\/h3>\n

To build and run Azure Service Fabric applications on your Windows development machine, install the Service Fabric runtime, SDK, and tools. You also need to enable execution of the Windows PowerShell scripts included in the SDK. Here<\/a> are instructions to setup your Windows development environment.<\/p>\n

Setup Azure Service Fabric Cluster<\/h3>\n

If you haven\u2019t already, setup the Azure SFC on Linux using the Azure Portal. For the OS version, select \u2018UbuntuServer 16.04-LTS\u2019 as shown in the picture below. Please check the following documentation<\/a> for more information on all other settings.<\/p>\n


<\/p>\n

\"clip_image002\"<\/a><\/p>\n


<\/h3>\n

Walkthrough: .NET Core Stateless Service Fabric Application <\/h3>\n

Step 1<\/strong>: In Visual Studio 2017, create a new Service Fabric Application<\/p>\n

New project > Visual C# > Cloud > Service Fabric Application<\/em><\/p>\n

\"clip_image004\"<\/a><\/p>\n

Click OK to select a Template \u2018.NET Core 2.0 Stateless Service\u2019<\/p>\n

\"clip_image006\"<\/a><\/p>\n

Step 2<\/strong>: Update the Runtime Identifier to linux-x64<\/p>\n

Open all the service .csproj<\/b> files and update the RuntimeIdentifier as shown below<\/p>\n

\n

<PropertyGroup><\/p>\n

<OutputType>Exe<\/OutputType><\/p>\n

<TargetFramework>netcoreapp2.0<\/TargetFramework><\/p>\n

<IsServiceFabricServiceProject>True<\/IsServiceFabricServiceProject><\/p>\n

<RuntimeIdentifier>linux-x64<\/RuntimeIdentifier><\/p>\n

<\/PropertyGroup><\/p>\n<\/blockquote>\n


<\/p>\n

Step 3<\/strong>: Update the ServiceManifest.xml to remove .exe <\/b>extension from Stateless1.exe to Stateless1 as shown below<\/p>\n

\n

<CodePackage Name=”Code” Version=”1.0.0″><\/p>\n

<EntryPoint><\/p>\n

<ExeHost><\/p>\n

<Program>Stateless1<\/Program><\/p>\n

<\/ExeHost><\/p>\n

<\/EntryPoint><\/p>\n

<\/CodePackage><\/p>\n<\/blockquote>\n

Note: If you are building for Windows, the entry point is Stateless1.exe but since you\u2019re building for Linux, it\u2019s not going to produce a Windows EXE file. Therefore, we have to change that in the ServiceManifest.xml to the binary output file that\u2019s being built for Linux (usually it\u2019s the same file name but without the .exe extension). <\/p>\n

Step 4<\/strong>: Right click on the Project and click Publish. In the Publish Service Fabric Application wizard, select the Endpoint for SFC cluster and then click Publish.<\/p>\n

\"clip_image002[1]\"<\/a><\/p>\n

You can login to the Azure Portal, select Service Fabric Cluster, and verify if the application is deployed successfully.<\/p>\n

\"clip_image010\"<\/a><\/p>\n


<\/h3>\n

Walkthrough: ASP.NET Core Stateless Service Fabric Application <\/h3>\n

Step 1<\/strong>: In Visual Studio 2017, create a new “out of the box” Service Fabric Application<\/p>\n

New project > Visual C# > Cloud > Service Fabric Application<\/em><\/p>\n

\"clip_image011\"<\/a><\/p>\n

Click OK to select a Template \u2018Stateless ASP.NET Core\u2019<\/p>\n

<\/b><\/p>\n

\"clip_image013\"<\/a><\/b><\/p>\n

Click on \u2018Web Application (Model-View-Controller)\u2019<\/p>\n

\"clip_image015\"<\/a><\/b><\/p>\n

Step 2<\/strong>: Update the Runtime Identifier to linux-x64<\/p>\n

Open all the service .csproj<\/b> files and update the RuntimeIdentifier as shown below<\/p>\n

\n

<PropertyGroup><\/p>\n

<OutputType>Exe<\/OutputType><\/p>\n

<TargetFramework>netcoreapp2.0<\/TargetFramework><\/p>\n

<IsServiceFabricServiceProject>True<\/IsServiceFabricServiceProject><\/p>\n

<RuntimeIdentifier>linux-x64<\/RuntimeIdentifier><\/p>\n

<\/PropertyGroup><\/p>\n<\/blockquote>\n

Step 3<\/strong>: Update the ServiceManifest.xml to remove .exe<\/b> extension from Stateless1.exe to Stateless1 as shown below<\/p>\n

\n

<CodePackage Name=”Code” Version=”1.0.0″><\/p>\n

<EntryPoint><\/p>\n

<ExeHost><\/p>\n

<Program>Web1<\/Program><\/p>\n

<\/ExeHost><\/p>\n

<\/EntryPoint><\/p>\n

<\/CodePackage><\/p>\n<\/blockquote>\n

Step 4<\/strong>: Click on Publish won\u2019t work like it did in example \u2018.NET Core Stateless Service\u2019 above. This has to do with an issue in VS packaging for Linux for ASP.NET Core projects. As noted above, this will be fixed in an upcoming release.<\/p>\n

Here are the steps which should work using dotnet<\/b> commands to publish.<\/p>\n

    \n
  1. Only use VS to create application package structure, right click on Applciation3 in solution explorer and select Package. This will create application package structure at c:\\user\\source\\Application3\\Application3\\pkg\\Debug<\/i><\/b>\n
  2. Open Command Prompt, cd to the directory containing the AspNetCore .csproj<\/b> (c:\\user\\source \\Application3\\Web1<\/i><\/b>) and run following commands:<\/li>\n<\/ol>\n
    \n

    dotnet build<\/b><\/p>\n

    dotnet publish –self-contained -r ubuntu.16.04-x64 -o <\/b>c:\\user\\source \\Application3\\Application3\\pkg\\Debug\\Web1Pkg\\Code<\/b><\/p>\n<\/blockquote>\n

    Step 5<\/strong>: Now use Service Fabric PowerShell to create the application.<\/p>\n

      \n
    1. Connect-ServiceFabricCluster mmlinuxsfc.eastus.cloudapp.azure.com:19000 (Provide security credentials if its secured cluster)\n
    2. Copy-ServiceFabricApplicationPackage -ApplicationPackagePath c:\\user\\source \\Application3\\Application3\\pkg\\Debug -ApplicationPackagePathInImageStore pkg_app3_cmd\n
    3. Register-ServiceFabricApplicationType -ApplicationPathInImageStore pkg_app3_cmd\n
    4. New-ServiceFabricApplication -ApplicationName  fabric:\/Application3Type -ApplicationTypeName Application3Type -ApplicationTypeVersion 1.0.0<\/li>\n<\/ol>\n

      Note: Register-ServiceFabricApplicationType occasionally times out. Use compression flag for faster uploads.<\/p>\n

      If Step 5 runs successfully, Application3 should be installed in SFC.<\/p>\n

      \"clip_image017\"<\/a><\/p>\n

      If the Application3 failed to upload or times out, you can use Azure Service Fabric CLI command, sfctl to upload the application. You can install the Azure Service Fabric CLI from https:\/\/docs.microsoft.com\/en-us\/azure\/service-fabric\/service-fabric-cli<\/a><\/p>\n

      After using the \u201csfctl application upload\u201d and \u201csfctl application provision\u201d. The ASP.NET 2.0 MVC service, is deployed to Linux SFC and healthy. <\/p>\n

      \n

      C:\\users\\pathwherphythoninstalled>sfctl<\/b><\/p>\n

      application upload –path <\/b>c:\\user\\source \\Application3\\Application3<\/b>\\pkg\\Debug –show-progress<\/b><\/p>\n

      C:\\users\\pathwherphythoninstalled>sfctl<\/b><\/p>\n

      application provision –no-wait –application-type-build-path Debug<\/b><\/p>\n<\/blockquote>\n

      Note: if Application has references to other project which has reference to NuGet packages, use the following workaround:<\/p>\n

      Compile the above project using the below command and save these binaries:<\/p>\n

      \n

      1. dotnet publish -c Release -r linux-x64<\/p>\n

      2. In Visual Studio, compile the Service Fabric project to generate the binaries<\/p>\n

      3. Replace the generated binaries with the ones generated in #1<\/p>\n

      4. Use SF CLI to upload the binaries and create the application<\/p>\n<\/blockquote>\n

      The application that has NuGet package reference has successfully started in the SF cluster<\/p>\n

      References<\/h3>\n