[C#]Reading Memory / Pointer with multiple Offsets.

01/09/2013 23:59 »jD«#16
Make sure you don't use that on a 64 bit program ;)

-jD
01/10/2013 01:55 iCraziE#17
why not? it wouldn't work?
Is it because of the conversions to Int32?
01/10/2013 03:09 »jD«#18
Yea. The reason I got you to add an IntPtr overload is the fact that an IntPtr will be a long (Int64) on 64bit machines and an int (Int32) on 32bit machines. When you explicitly cast them to a 32bit integer it removes support for some 64bit applications. I would recommend sticking with an IntPtr the entire way and changing the signature of your method to take an IntPtr instead of an Int32.

Just my oppinion tho :)

-jD
01/10/2013 04:52 iCraziE#19
Ah okay, well ill keep that in mind. Fortunately the application is 32-bit so this is fine for me.
01/10/2013 04:56 »jD«#20
Sure :) Got anymore questions?

-jD
01/12/2013 00:08 iCraziE#21
I noticed something weird in my application. I believe the cause is the memory reading functions.

Even if I don't run my application. If I open the target exe for reading memory, I wont be able to move,rename, or delete my application. I get the error that it is already running in the target exe.
01/12/2013 01:05 »jD«#22
Did you call close handle in the read memory function?

-jD
01/12/2013 05:57 iCraziE#23
Sure did. The same way you told me to. But it's weird, I think its the exe im attaching to itself, not my application.

I almost positive it has to do with the game crashing. (the game detects visual studio as a third party program lmao) And somehow the processes think that the game is still oepn and its still attached to the game. it weird, i noticed the same results when using autoit, if i compiled it into an exe.
01/12/2013 06:49 »jD«#24
Try running in Detached mode. Hit Ctrl+F5 to run with the debugger disabled.

-jD