Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Extract libgit2 at runtime #3
Unfortunately, while Visual Studio has many solutions for ensuring that
The easiest, most foolproof method to ensure that a managed DLL has its
That's brilliant! I like it very much.... even if it doesn't compile ;)
Depends, but it probably would work. I make no guarantees though.
This is changing the environment variables of the process, it doesn't affect any other user. It's important to leave this in because we can't guarantee that the DLL will be in the Loader search path otherwise. On my machine, not doing this means all the unit tests fail.
Keep this too, the entry assembly is one of the places searched in the Loader search path.
Hm. I've made some research. Considering the "by default" configuration of medium trust hosted environment and Azure, extracting (either in the app/bin dir or in the temp directory) would make us jump through many hoops.
Sorry about this. You're right.... and inspiring!
So, if we strike off the extraction, we go back to SqlCe scenario: Next to the managed assembly, a folder
However, instead on relying on
The added path would be a combination of the original location of LibGit2Sharp (
Do you think this would work on your machine?
They can always deploy libgit2.dll themselves. There's no reason for us to bend over backwards to support a scenario that is marginal at best.
Paul Betts firstname.lastname@example.org
On Monday, October 3, 2011 at 1:11 PM, nulltoken wrote: