Replace current implementation of communication with the Windows Event Log with a NuGet package

[aplteam]

The current implementation works fine with .NET 3.1 (formerly known as .NET Core).

It causes for reasons that probably even Microsoft cannot explain a VALUE ERROR after .NET got upgraded to 6.0 (not called .NET Core anymore, so let's call this .NET-not-Framework - tx Microsoft for the clear and well-defined naming that has been so reliably inconsistent over the years.

Apparently this can be overcome by using the NuGet package called System.Diagnostics.EventLog.

[aplteam]

Requires NuGet being fully functional which is not the case for the time being, therefore delayed for 2.0

[mkromberg]

I think you are looking for an enhanced .NET bridge, rather than a change to NuGet itself? BTW, I am surprised that a .NET component like System.Diagnostics.EventLog would require features that are not already supported. Have you checked or is this comment mostly expressing pessimism? :)

[aplteam]

Yes, that is correct. I have not actually checked whether generics are required in this case TBH.

We need to prioritize work, so it seemed fair to say, "Let's revisit this once Generics are supported by the bridge." This is particularly true because right now, one CAN install a Windows Service, though not as a NuGet package.