Skip to main content

Cum sa controlam modul in care un serviciu windows porneste din cod

Prin intermediul la clasei ServiceController putem sa controlam un serviciu windows. Il putem in orice moment porni sau oprii. Dar daca avem nevoie sa ii schimbam startup type? De exemplu daca vreau sa ii schimb startup type-ul de pe manual pe automat?
Din pacate ServiceController nu ne oferă aceasta funcționalitate. Din cod C# nu am gasit o posibilitatea prin care as putea sa fac acest lucru. In schimb am gasit in registry bine ascunse aceste valori.
Daca deschidem registrii si ne uitam sub Local System in path-ul "SYSTEM\CurrentControlSet\Services\" o sa gasim lista cu toate serviciile pe care le avem instalate pe masina. Pentru fiecare serviciu avem:
  • nume
  • descriere
  • tipul
  • startup type-ul
  • path-ul spre serviciu
  • etc
Daca schimbam una din aceste valori, sistemul de operare o sa faca update automat la serviciu. O solutie la probleme noastra este sa facem o metoda care scrie valoarea in registri.
public enum StartupModeType
{
Boot = 0,
System = 1,
Automatic = 2,
Manual = 3,
Disabled = 4
}
Mai sus este lista cu starile pe care le poate avea serviciu. Iar mai jos avem cele doua metode care fac get si set la aceasta valoarea:
public StartupModeType GetStartupMode(string serviceName)
{
RegistryKey registryKey = Registry.LocalMachine.OpenSubKey(""SYSTEM\\CurrentControlSet\\Services\\" + serviceName);
StartupModeType startupMode = (StartupModeType)registryKey.GetValue("Start");
registryKey.Close();
return startupMode;
}
public void SetStartupMode(string serviceName, StartupServiceMode startupServiceMode)
{
RegistryKey registryKey = Registry.LocalMachine.OpenSubKey("SYSTEM\\CurrentControlSet\\Services\\Start",RegistryKeyPermissionCheck.ReadWriteSubTree);
registryKey.SetValue(StartupTyeRegistryKey,(int)startupServiceMode);
registryKey.Close();
}
In functie de necesitati putem sa facem niste extension methods la ServiceController care sa se ocupe de acest lucru. O alta varianta era cream un proces nou si sa apelam "sc [numeServiciu] config".

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...