Michael Clayton

A couple of other cases where PowerShell's unrelenting attempts to convert function parameters into *something* that an overload supports give surprising results: * ```"source target destination".Split("target")``` - in PowerShell 5.1...

So it looks like adding ```true``` to MouseJump.Common.csproj has fixed the problem with ```verifyDepsJsonLibraryVersions.ps1``` detecting a different version of ```System.Drawing.Common.dll``` being referenced in MouseJump.Common versus all the other modules. I'm...

I think this PR is ready for review now - the manual and automated tests all work and the build pipeline is green. The only remaining piece of work is...

Fixed a bunch of merge conflicts - build is working again.

@jaimecbernardo - just a quick head-up - before this gets merged into main the new MouseJump.Common.dll needs to be added to the installer, which I wasn't confident about doing myself...

> Hi @mikeclayton , I've given it a try but after building in Visual Studio the MouseJump exe doesn't seem to be created. Can you please try building the PR...

Looks like I removed these from the MouseJumpUI.csproj and MouseJump.Common.csproj somewhere along the line... ``` false false ``` so it was building in the wrong folder. I'll re-add them later...

@jaimecbernardo - the latest commit appears to put the build output in the right location now when I run it locally.

Just reading some old issues - I had a play with something along these lines in the past but the Find My Mouse code was a bit beyond me so...