oicguy

If I were using MSBuild directly, I'd need to use `msbuild.exe /p:MSBuildExtensionPath="C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild"`. Obviously that specific for my computer since not everyone would use the C: drive...

That's all I can really ask for. Thanks for at least considering it.

I'm not sure if you read the solution for that issue link but it says that flaky behavior is a bug in MsBuild 3.5 and the post itself is over...

I think this solution is fine and I can't wait to test it against my application. Thanks!

So ummm, can we get a release for this #85 since it was merged?