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");
return startupMode;
public void SetStartupMode(string serviceName, StartupServiceMode startupServiceMode)
RegistryKey registryKey = Registry.LocalMachine.OpenSubKey("SYSTEM\\CurrentControlSet\\Services\\Start",RegistryKeyPermissionCheck.ReadWriteSubTree);
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".


Popular posts from this blog

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 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.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…