i can't call demo method，it report: System.AccessViolationException

[Charltsing]

project(vs2022 ,net framework 4.72)
demo.zip

Did I make any mistake?

[trungnt2910]

Which version of the library are you using? The prerelease versions have known problems.

[Charltsing]

Latest version

[trungnt2910]

The latest version has bugs (#34)

You might want to use MemoryModule.NET version 0.1.0 on NuGet instead.

[Charltsing]

The latest version has bugs (#34)

You might want to use MemoryModule.NET version 0.1.0 on NuGet instead.

i try 0.1.0, but it has the same problem

maybe someting is wrong?

[Charltsing]

https://github.com/wwh1004/MemoryModule,
MemoryModuleLite

it works fine

[trungnt2910]

It seems like my implementation is getting the wrong address, off by 0x10000 bytes.

I am looking into this, haven't touched this code for quite a long time.

[trungnt2910]

Your example works fine on my new branch (https://github.com/trungnt2910/MemoryModule.NET/tree/dev/trungnt2910/Abstractions), where I wrote the PE loader from scratch.

My old branch was ported from the old MemoryModule C code, and to be honest I don't really understand what it is. The new one was created from scratch using a new design.

The only problem preventing this branch to be merged into master is #34. The approach of hooking TLS functions seems to not work on Windows since Windows does not have a dedicated function for TLS handling, instead Windows applications directly access the segment registers FS and GS.

I do not currently have much time to work on this project, but I would be grateful if you have any suggestions on how to fix this particular issue on the master branch.

[Charltsing]

I hope to load dll with minimal code, MemoryModuleLite looks good

[Charltsing]

https://github.com/bb107/MemoryModulePP/blob/master/MemoryModule/MmpTls.cpp
https://hub.njuu.cf/bb107/MemoryModulePP/blob/master/MemoryModule/MmpLdrpTls.cpp

[trungnt2910]

I am aware of that repo, seems like it requires hooking some low-level thread lifetime functions that I don't understand yet.

[trungnt2910]

Sorry for the delay, but this issue should be fixed in the latest version. Please check the NuGet library for the latest review.