Skip to main content

Auto-start la servicii WCF hostate pe IIS

Sunt cazuri când avem servicii WCF pe IIS care necesita un timp lung pentru iniţializare. Din aceasta cauza primul apel a unui serviciu poate sa dureze o veşnicie.

La încărcarea aplicaţiei, IIS ne ajuta destul de mult: iniţializează AppDomain, compilează dacă este nevoie codul( în principiu pregăteşte aplicaţia). Aproape totul este pregătit, mai puţin iniţializarea serviciilor, care este lăsata în seama noastră.

Pentru aceasta problema exista mai multe soluţii:

  • La iniţializarea aplicaţiei se pot încarcă resursele necesare serviciului static sau într-un IoC.
  • Apelul "virtual" a tuturor serviciilor, în momentul în care serverul porneşte. Prin aceasta metoda toate resursele folosite de către servicii o sa fie deja încărcare.
  • Implementarea unui mecanism de auto-start la servicii.

O sa descriu mai amănunţit ultima soluţie propusa. .NET împreuna cu IIS 7.5 ne pune la îndemâna un mecanism destul de simplu prin intermediul căruia putem sa iniţializam automat un serviciu şi sa controlam obiectele care sa se iniţializează în acel moment.

Primul pas este sa selectam în IIS aplicaţia care conţine serviciile şi sa selectam Manage WCF andWF Services. Aici trebuie sa activam Auto-Start. In acest moment toate serviciile o sa fie pornite automat.

Următorul pas este sa găsim o modalitate prin care putem sa controlam modul în care fiecare serviciu este iniţializat. Pentru acest lucru este nevoie sa cream un service host factory personalizat. Pentru acest lucru este nevoie sa cream o clasa ce moşteneşte ServiceHostFactoryBase. Prin intermediul metodei CreateServiceHost putem sa executam orice cod care dorim sa fie rulat la iniţializarea serviciului, trebuie doar sa avem grija sa returnam instanta a unui ServiceHost.

public class ValidateServiceHostFactory : ServiceHostFactoryBase
{
public override ServiceHostBase CreateServiceHost(string constructorString, Uri[] baseAddresses)
{
//Custom code folosit pentru incarcarea anumitor servicii;
InitValidateService(baseAddresses);
return new ServiceHost(typeof (ValidateService), baseAddresses);
}
}
Tot ce ne-a mai rămas de făcut este în .SVC sa adaugăm la atributul Factory cu locatia ServiceHostFactory pe care noi l-am implementat:

<%@ ServiceHost Language="C#" Debug="true" Service="Services.ValidateService" CodeBehind="ValidateService.svc.cs" Factory="Services.Factory.ValidateServiceHostFactory " %>
Gata, avem un serviciu care porneşte automat la iniţializarea aplicaţiei în IIS, la care putem sa controlam ce resurse sa se iniţializeze prin factory.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...