Pitt

@jahav Please reopen. I tried your fix, but still getting the same error. I slightly adjusted my example from above and set the number format only to the data cell....

seems like nuget package cache is not updating the files in if package name/number is identical. Obviously i had an older -preview.nupkg in use. After cleaning this up and using...

I updated to Git for Windows 2.5 64bit as recommended. GitFlow reports now "Could not locate Git for Windows". I reinstalled Git and GitFlow, but the error still occurs. SourceTree...

Whats the matter with 64bit? SourceTree is also 32bit, but can use 64 git. It is just the path to the executable, right?

Standard Installation: "C:\Program Files\Git" . Is there a log file with further information?  Thx for looking into this.

I checked the different code pathes ... first of all, i had a remaining invalid PATH entry from a former git installation pointing to the wrong directory. But problem is...

i traced with procmon what is going on behind the scenes. It seems that the 64bit code pathes are not executed. Registry: HKLM is searched only for 32bit, the 64bit...

version 0.10.12.0 and there is no Git folder below Program Files (x86).

I tried, but no change. I looked to your coding changes: No one would apply for me. 1st i cleaned my PATH variable. The procmon output has shown that it...

still does not work. It is still looking at the wrong place. I'm using the 64bit GitforWindows. The registry key is HKLM\Software\GitForWindows. VisualStudio is looking here: HKLM\SOFTWARE*_WOW6432Node_*\GitForWindows (traced with procmon)...