-
-
Notifications
You must be signed in to change notification settings - Fork 801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use LibGit2Sharp #37
Comments
Progress so far is in my libgit2 branch if anyone wants to test it out. PowerShell is blowing up in amd64 mode and I can't figure out why. See also libgit2/libgit2sharp#128 /cc @tclem @xpaulbettsx @haacked @nulltoken |
@dahlbyk does it work if you keep the initial directory structure? Are you sure the process environment Path variable you set is the same that the one which is being accessed in NativeMethods static constructor? |
"Initial directory structure" -> relatively to the LibGit2Sharp.dll |
Ah, did not notice that DLL location logic - will try. |
Pushed an update using the initial directory structure. Still blows up on amd64. This works fine:
However calling |
Are you able to access, from PS, simple What kind of exception do you encounter?
If you can provide me with some failing C# code, I'll take the burden :) |
And...I can't repro in a console app. :( This is what Windows reports for the PowerShell crash:
|
@xpaulbettsx would you be able to provide some ninja debugging help here? |
I'm on it, will check it out tomorrow Paul Betts On Sunday, April 8, 2012 at 12:18, nulltoken wrote:
|
@dahlbyk Can you still reproduce this against the latest vNext tip? |
Yes, as far as I can tell I'm getting the same error, still only on amd64. I'll see if I can look at this with @xpaulbettsx while we're in the same room. |
Callback issue has been merged in |
CA-1441: Updating Scotia mock driver
Looks like we are still using git.exe and given that MS has switched with VS 2017 to use git.exe instead of some variant of libgit, maybe we just close this issue? |
Hopefully faster than multiple git calls...
The text was updated successfully, but these errors were encountered: