Dear Sirs,
I'm a .NET developer with 15+ years of experience. I worked on both desktop and web development projects, using both major .NET languages - C# and VB.NET. My recent experience is with ASP.NET MVC, RESTful services, jQuery, Bootstrap, SignalR, ASP.NET Identity, MS SQL server, Entity Framework. In 2014 I took the Microsoft Exam 70-486 and got certified for development of ASP.NET MVC Web Applications.
Throughout my career I've been part of multiple teams, developing various systems, so I gain experience in many areas, regarding Windows programming, including Windows Services.
My approach would be to study and analyze the business requirements in order to prepare the "product backlog". This involves heavy communication with the business (you) so I could understand the specific needs. So, don't hesitate to contact me and discuss further!
Limitations:The bigger limitation of Windows services is the lack of a desktop session to interact with. But with some unmanaged calls this limitation could become just an obstacle.
Display detected events: The events needs to be displayed in real time only if there is a logged on user. So Win32 calls could help and spawn a process to the user desktop directly from within the service process. But this is the harder way. The easiest one would be to write a program and start it upon logon - startup folder, scheduled task, registry entry. From there, a NotifyIcon would be sufficient to display a message in the tray ...