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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP