EasyHook full changelog

released updated Nuspec/Nuget with content files (#297)

x64 trampoline: ensure stack is 16 bytes aligned

x64 trampoline: ensure stack is 16 bytes aligned

CreateAndInject now supports long command lines (#84 / #170)
RhCreateRemoveStealthThread now works for 64-bit targets (#91 / #159)
Added LhGetHookBypassAddress / LocalHook.HookBypassAddress to allow bypassing the hook and call original directly without having to be within the hook handler (#155)

EasyHook crashing targets, RhInjectLibrary on Win7 64bit, 32bit process, 32bit injection dll + launcher application = problem - now determines the address of GetProcAddress etc by reading the remote process' PE image
Easyhook was not unloaded when host is closed, Allow RemoteHook unloading - managed EasyHook.dll and user assemblies are now loaded into a new AppDomain which is then unloaded when the custom IEntryPoint Run method returns. A new assembly - EasyLoad32/64.dll - that makes use of managed DllExport's provides a more stable .NET framework initialisation.
FileMon example updated to no longer require the GAC

Hooking of CreateFile fails on Win 8.1 x64, Compatiblity With Windows Server 2012 And 8, Crashed Notepad in Win 8 64-bit, 2.7 FileMon crashes 64-bit processes, Do not work on Windows8 x64., relative mov in EntryPoint not handled - correctly relocates RIP addresses (64-bit). Windows 8/8.1 kernel32 APIs now all use RIP addressing when passing through to kernelbase.
Command-line arguments problem in RtlCreateSuspendedProcess - command line correctly passed through
Bug in RtlGetLastErrorString, RtlGetLastErrorString() returns empty string for invalidate parameter - fixed marshalling bug with RtlGetLastErrorString across managed boundary
Severe bug: LhWaitForPendingRemovals hangs forever - LhWaitForPendingRemovals endless loop under certain circumstance
Compiling 2.7 on VS 2012 fails with some issues - support for VS2012
Host process crashes when unloading hooks - fixed crashes when unloading 64-bit hooks. This also fixes the crash within the ProcessMonitor sample.

· Alpha 2 release of 2.7, adds .NET 4 support and ability to hook without registering assemblies into the GAC
· Note: binaries compiled for .NET 2.0. Source has also been tested with .NET 4.0 Client Profile and confirmed to work
· Requires Visual Studio 2010 to compile
· The ProcessMonitor has been compiled for AnyCPU and also explicitly for Win32. This is be able to easily test the WOW64 bypass if injecting from 64-bit to 32-bit

· Alpha release of 2.7, adds .NET 4 support and ability to hook without registering assemblies into the GAC
· Requires Visual Studio 2010 to compile
· The ProcessMonitor has been compiled for AnyCPU and also explicitly for Win32. This is because the 2.7 release is currently only working if injecting from a 32-bit to a 32-bit, and from 64-bit to 64-bit