azure-service-fabric

I want to be able to configure placement constraints based on different node types (i.e. FrontEnd, BackEnd). Can I do this per-environment, so that in my test/local cluster there are no constraints, but on my production environments there is? aoetalks Yes, you can! The official docs describe a way to do this via code, but you can also do so with the service manifest files directly to get default & per-environment configuration. There is a blog post you can follow (found it in this answer ). 来源： https://stackoverflow.com/questions/40558124/how-do-i-configure-service-fabric-placement-constraints

When creating an ASP.NET Core app an environment variable called ASPNETCORE_ENVIRONMENT=Development will be set for you and when debugging you will see that the IHostingEnvironment is set to Development . The problem is that when I use the same project in a solution set up for Service Fabric the environment variables don't seem to get injected and IHostingEnvironment just returns "Production". How can I resolve this? Note: I've set a breakpoint in the startup class to observe the IHostingEnvironment variable. Reference for this answer: https://docs.microsoft.com/en-us/azure/service-fabric

I am looking to have a generic type service ie - public interface IFooService<T> { Task<T> Get(int id); } However, service fabric does not allow generic classes or generic methods. I have also tried something like public interface INinjaService : IService, IFooService<SuperNinja> { } but it does not pick up inherited interfaces stating The service type 'Omni.Fabric.Services.NinjaService' does not implement any service interfaces. A service interface is the one that derives from 'Microsoft.ServiceFabric.Services.Remoting.IService' type. I can't seem to find any reference to generics on Service

I want to use the WebJob SDK in a stateless service running as a Service Fabric application. Unfortunately I’m not able to get it running properly. Below is part of a test code that reproduces the problem. The “ProcessMethod“ is never invoked. The triggered function “ProcessNotificationsInQueue“ is also never executed (yes, there are items in the queue). The “Health State” of the application is set to “Error” in the Service Fabric Explorer although the application is still running. The DashboardConnectionString and StorageConnectionString both have the correct values. I don’t see any problem

I have a application that can be broken down into multiple communicating services. My current implementation is monolithic and I want to reorganize it so that individual components can be deployed,iterated upon, scaled independently. I see two ways to do this with Azure: Service Fabric service composed of set of communicating micro-services (stateless, web-api etc.) A collection of individual Azure Web Apps/ Cloud Services that call each other at the http end points. Are there any obvious advantages of 1 over 2? Any rule of thumb to chose one over the other would also be very helpful. Peter

I downloaded the latest version of Service Fabric SDK 2.4.164 and try to create a new simple stateless service. Build succeeded but when I run it to debug I got: An unhandled exception of type 'System.BadImageFormatException' occurred in Unknown Module. Additional information: Could not load file or assembly 'System.Fabric, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An attempt was made to load a program with an incorrect format. What is the problem? Please help to solve that. Let me know if I have to add more informations Azure Service Fabri