Martin Storø Nyfløtt

I have the same issue: ``` Install-Package: C:\program files\powershell\7\Modules\PowerShellGet\PSModule.psm1:9709 Line | 9709 | … talledPackages = PackageManagement\Install-Package @PSBoundParameters | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | The following commands are already available on this system:'Get-Uptime'....

Look in the samples folder under src, there are plenty of examples there to get you started.

This is actually pretty bad. If the TCP connection gets closed (this can be quite normal), NLog has no internal mechanism for observing that the connection has been gracefully closed....

@snakefoot I wasn't thinking of performing any connection checking, but simply add support for listening for the connection to be gracefully closed. All in all, I simply register a receive...

@snakefoot Actually, neither. I don't want to mess with any socket parameters since I want to get a general solution to this problem. Different systems (routers/endpoints/whatever) may act differently with...

@snakefoot Sorry for the delay, got quite busy the past few days ... :( I've managed to scramble something together, I haven't tested it out but I think it's a...

@snakefoot I don't see any reason implementing it synchronous as the APIs being used in NLog are asynchronous. I went a bit back and forth with how to approach it...

@snakefoot Don't think that will be a good idea since then you face the issue where you risk receiving the same data multiple times between reconnections. To deal with that...

@snakefoot If you partially receive a log message (at the server) and the connection dies, you reconnect and send the whole thing again you could end up with parts (or...

@snakefoot Sorry, my bad I misread your comment, considering the `_pendingRequest`, I agree it would make sense to reconnect to the server and send what is left in it until...