Darrell

Thank you - much appreciated, that should save me quite a bit of time there!

It's most likely due to this: https://github.com/GitTools/GitReleaseNotes/issues/111

@gep13 I couldn't find the update on chocolatey. https://chocolatey.org/packages/GitReleaseNotes.Portable I am currently running via the chocolatey package. Any chance this could be released there? Or do we now get it...

For the msbuild task, sadly, we'd need #168 first, as the travis build runs on linux, and we use the dotnet cli tooling in order to build. Think for now...

i am seeing the same error, but I am not skipping negotiation. The client tries to send a negotiate request and get's an error 500 response > Request URL: https://foo-dev-pr167.azurewebsites.net/hubs/webnotifications/negotiate?negotiateVersion=1...

- the reason I think this might be a problem is in a microservice landscape, some services might be updated before others. If multiple services are using the semaphore and...

One solution (workaround) I can think of involves consumers of this library reading their semaphore slot counts from some global config. So for example you might have some globally accessbile...

In terms of a lock escalation strategy, I think it would make sense to escalate in this mannor: 1. Local process 2. OS Level 3. Some external coordinator (i.e sql...

> I'd be interested to hear about what the 3-level scenarios are that you've encountered. Not many! I was just thinking purely conceptually that this order makes sense. The only...

> Until then, the FileDistributedLock class should provide a cross-platform approach to OS-level locking. Good point! I haven't looked at the implementation - but has this been tested / used...