EasyHook Practical Guide
The so-called practical guide is full of dry goods, not so many things virtual first Pakistani Brain, the real use of people will find useful things for themselves, kick the tires of people will look unintelligible.
FileMon real problems of our own doing encountered:
1. exe and dll file must be strongly named for VS2010 it can set in the project properties, without having to manually generate the command line and then manually adding, location in the "Project Properties" -> "signature" -> select "for the Assembly signature "in the drop-down box and select" <New ...> ", you can enter an appropriate name.
There is no strong-named error message similar to: Assembly generation failed - Referenced assembly "WindowsHook" no strong name
2. If you use EasyHook in VS2010, you must use the latest version 2.7, because the previous stable version 2.6 is .NET 2.0, 4.0 there will be problems in the environment, then based, of course, if you want to use a certain version 2.6, in theory, everything must be done with .NET 2.0, like to take this path students can try it for yourself, I will not accompany you.
3.EasyHook.dll should only true 32-bit and 64-bit proxy dll file, so when used in addition to EasyHook.dll to add a reference, we also need these four files (EasyHook32.dll, EasyHook32Svc. copying together exe, EasyHook64.dll, EasyHook64Svc.exe) run directory, or you'll run into "Unable to run internal command." error.
Being on so much, not much dry, but really useful for people who, in a word can save several hours of searching, That's all!
The so-called practical guide is full of dry goods, not so many things virtual first Pakistani Brain, the real use of people will find useful things for themselves, kick the tires of people will look unintelligible.
FileMon real problems of our own doing encountered:
1. exe and dll file must be strongly named for VS2010 it can set in the project properties, without having to manually generate the command line and then manually adding, location in the "Project Properties" -> "signature" -> select "for the Assembly signature "in the drop-down box and select" <New ...> ", you can enter an appropriate name.
There is no strong-named error message similar to: Assembly generation failed - Referenced assembly "WindowsHook" no strong name
2. If you use EasyHook in VS2010, you must use the latest version 2.7, because the previous stable version 2.6 is .NET 2.0, 4.0 there will be problems in the environment, then based, of course, if you want to use a certain version 2.6, in theory, everything must be done with .NET 2.0, like to take this path students can try it for yourself, I will not accompany you.
3.EasyHook.dll should only true 32-bit and 64-bit proxy dll file, so when used in addition to EasyHook.dll to add a reference, we also need these four files (EasyHook32.dll, EasyHook32Svc. copying together exe, EasyHook64.dll, EasyHook64Svc.exe) run directory, or you'll run into "Unable to run internal command." error.
Being on so much, not much dry, but really useful for people who, in a word can save several hours of searching, That's all!