azure-service-fabric

Does Azure Service Fabric do the same thing as Docker?

由 假装没事ソ 提交于 2019-11-30 11:21:42
问题 My thinking is that people use Docker to be sure that local environment is the same as production and that I they can stop thinking about where are their apps running physically and balancing mechanisms should just allocate apps in best places for that moment. I'm 100% web based and I'm going to move to cloud together with our databases, and what cannot be moved will be seamlessly bridged so the corporate stuff and the cloud will become one subnetwork. And so I'm wondering, maybe Service

Azure service fabric actor dependency injection

由 懵懂的女人 提交于 2019-11-30 11:05:40
Is there any way to inject dependencies in to the Azure Service Fabric Actor's constructor? Having had a bit of a dig-around in this area with dotPeek a while back (trying to resolve actors from an Autofac lifetime scope per-invocation), I think the trick is to create your own implementation of StatelessActorServiceFactory, and your own extension method to register the actor with it. Although the factory class is marked as internal, its interface (IStatelessServiceFactory) and the service type it creates (StatelessActorServiceInstance) are both public. Unfortunately, it doesn't look like

Azure Service Fabric missing DLL on production server: FabricCommon.dll

由 一个人想着一个人 提交于 2019-11-30 09:33:26
I have created an actor service, which runs on a development cluster. An ASP.NET application (hosted separately via IIS), connects to the cluster and uses the actors. This works fine. But when I deploy everything to the production environment, the ASP.NET application fails to connect to the cluster with the below exception. The cluster is hosted on-premise (Windows 2012 R2). The type initializer for 'Microsoft.ServiceFabric.Services.ServiceTrace' threw an exception. Stacktrace: at Microsoft.ServiceFabric.Services.Common.FabricServiceConfig.TryGetConfigPackageObject(String configPackageName,

Microsoft Service Fabric Host Service (FabricHostSvc) Hangs on Start

由 ≡放荡痞女 提交于 2019-11-30 07:18:10
I've been working with Microsoft Service Fabric since November 2015 and have encountered many issues but now Service Fabric has become completely non-functional on my development machine. Uninstall/reinstall doesn't help. I was using 1.5-preview and have since tried 2.0 to no avail. The problem started when I attempted to run a Service Fabric Application from Visual Studio 2015 Update 1 (as I have done hundreds of times over the past few months). My machine blue-screened (first time I've seen a Windows 10 blue screen). After rebooting, I was unable to get my Service Fabric Application to

Advantages of Service Fabric Microservices vs Collection of Azure Cloud services/web apps

由 喜欢而已 提交于 2019-11-30 05:40:59
问题 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

Environment variables not being used when debugging through a Service Fabric project

由 泄露秘密 提交于 2019-11-30 05:36:31
问题 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

Removing application from service fabric cluster

由 夙愿已清 提交于 2019-11-30 05:26:10
I tried removing application from service fabric using service fabric explorer. I deleted my application using Delete Application action. Then When I tried Unprovision application type I got error saying, Error: Application Type of version 1.0.0 could not be unprovisioned as it still contains active applications. I could see that even after deleting the application , the actor service inside the application is still active in some of the nodes. Am attaching a screenshot of my service fabric explorer. Any help regarding completely removing the applications? This can happen if services in your

WebJob SDK not working when running in a Service Fabric application

由 白昼怎懂夜的黑 提交于 2019-11-30 05:21:39
问题 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

Service Fabric System.BadImageFormatException

由 本秂侑毒 提交于 2019-11-30 05:20:13
问题 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

Azure Service Fabric Actors - unhandled exceptions?

由 六眼飞鱼酱① 提交于 2019-11-30 03:59:18
Right now our ASF cluster is running: Web API project - stateless and public facing Actor project - mostly volatile, keeping data in memory, used by certain APIs We are trying out Application Insights, and I can setup unhandled error tracking like their docs here have for our Web API project. Issue is, I want this for our Actor project as well. Is there a global place for catching unhandled errors within an Actor? I know it's new, and maybe that is why I can't find documentation on this. Right now I'm doing this inside every actor method, but doesn't seem like a great solution: public async
订阅 azure-service-fabric