Skip to main content

CRUD operation on Windows Task from .NET

Zilele trecute am gasit o librarie simpla si foarte usor de folosit pentru a crea task-uri sub Windows. Aceasta poarta numele de Task Scheduler Managed Wrappe si o puteti gasi la urmatoarea adresa: http://taskscheduler.codeplex.com/
Primul lucru care mi-a atras atentia a fost cat de usor se poate integra intr-o aplicatia deja existenta.
Clasa de baza, in jurul careia se invarte totul este TaskService, prin intermediul caruia putem sa inregistram task-uri noi sau sa le manipulam pe cele deja existente. Fiecare task se identifica unic printr-un nume. Pe baza acestui nume putem sa obtinem un task deja existent.
La fiecare task putem sa inregistram una sau mai multe actiuni care sa se execute. Actiunile pot sa fie de orice fel, incepand de la trimiterea unui email sau rularea unui executabil pana la afisarea unui mesaj la utilizator.
Acelasi lucru se intampla si cu trigerurile, toate cele existente pe Windows exista si in aceasta librarie:
  • EventTrigger
  • DailyTrigger
  • WeeklyTrigger
  • MonthlyTrigger
  • IdleTrigger
  • TimeTrigger
  • RegistrationTrigger
  • BootTrigger
  • LogonTrigger
  • SessionStateChangeTrigger
Pentru a adauga, sterge sau controla un task este nevoie sa ne cream o instanta de tip TaskService. Prin intermediul ei putem sa manipulam orice task de pe calculatorul curent sau de pe orice alt calculator.
Mai jos gasiti un exemplu de cod in care am creat un nou task. Modul de logare ii setez pe baza de token si va rula cu drepturile userului curent. Iar apoi setez task-ul sa ruleze odata la 12 ore si la fiecare logare in sistem a utilizatorului. La fiecare executie a acestui task, un fisier executabil urmareaza sa fie apelat.
using (TaskService taskService = new TaskService())
{
TaskDefinition taskDefinition = taskService.NewTask();
taskDefinition.RegistrationInfo.Description = "Description";
taskDefinition.Principal.LogonType = TaskLogonType.InteractiveToken;

var interval = new TimeTrigger();
interval.Repetition.Interval = TimeSpan.FromHours(12);
taskDefinition.Triggers.Add(interval);
taskDefinition.Triggers.Add(new LogonTrigger());

taskDefinition.Actions.Add(new ExecAction("doWork.exe", null, null));

taskService.RootFolder.RegisterTaskDefinition("TaskService playground task", taskDefinition);
}
Orice setare a unui Task am gasit-o mapata in aceasta librarie ajutatoare si decat sa folosesc interop pentru a lucra cu task-urile din Windows, prefer sa folosesc aceasta librarie. Pana acuma nu am avut nici o problema cu ea.

Enjoy!
Enjoy it!

Comments

  1. Si ea nu foloseste in spate tot interop?!

    ReplyDelete
  2. Da, in spate tot interop se foloseste. Dar decat sa imi fac maparea proprie, am gasit aceasta librarie, care are totul mapat destul de dragut. De exemplu valorile magine din interop de la 1 la x pentru anumite configuratii sunt mapate ca si enum-uri.
    Fiind de codeplex, codul sursa este disponibil, asa ca orice lucru custom se poate face destul de usor. Plus ca dupa ce am adaugat referinta la assembly, in 2-3 minute deja aveam primul task creat.

    ReplyDelete
  3. Intrebarea e: permite crearea si planificarea de taskuri custom, reprezentate de un assembly sau clasa creata de developer, nu doar .exe-uri?
    Altfel, ramane ceva util mai mult pentru un sistem admin care doreste sa faca un script care sa-i ruleze diverse actiuni..

    ReplyDelete
  4. Nu, nu suporta acest lucru. Ca sa faci asa ceva e destul de complex. S-ar putea implementa ceva custom care intr-o locatia data( registri de exemplu) sa faca store la locatia unde este assembly-ul care trebuie rulat. In acest caz ai avea nevoie si de o parte din aplicatie care face acest lucru sa fie instalata pe masina.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too