rebasing | 易学教程

.NET assemblies and DLL rebasing

阅读更多关于 .NET assemblies and DLL rebasing

问题 According to this article rebasing is not necessary for .NET assemblies due to JIT compilation of the code. The article states: "JIT-compiled code does not have a rebasing problem since the addresses are generated at run time based on where the code is placed in memory. Also, MSIL is rarely affected by base address misses since MSIL references are token-based, rather than address-based. Thus when the JIT compiler is used, the system is resilient to base address collisions." However, I have

.NET assemblies and DLL rebasing

阅读更多关于 .NET assemblies and DLL rebasing

If I want to rebase my DLL's, how do I go about doing it?

阅读更多关于 If I want to rebase my DLL's, how do I go about doing it?

问题 This is a continuation of this question. I'm in the process of testing whether rebasing the .NET DLLs, and NGENning them will provide me with more shared code in memory on terminal servers. However, my plan seems to have a flaw, and it's that I seem unable to find a working method to figure out a working set of addresses. What I thought I could do was as follows: Just build and NGEN everything Start the program, ensuring all the DLL's have been loaded Use LISTDLLS /R PROGRAMNAME to get a list

.NET assembly cache / ngen / jit image warm-up and cool-down behavior

阅读更多关于 .NET assembly cache / ngen / jit image warm-up and cool-down behavior

问题 I have an Input Method (IME) program built with C#.NET 2.0 DLL through C++/CLI. Since an IME is always attaching to another application, the C#.NET DLL seems not able to avoid image address rebasing. Although I have applied ngen to create a native image of that C#.NET 2.0 DLL and installed it into Global Assembly Cache, it didn't improved much, approximately 12 sec. down to 9 sec. on a slow PIII level PC. Therefore I uses a small application, which loads all the components referenced by the C

If I want to rebase my DLL's, how do I go about doing it?

阅读更多关于 If I want to rebase my DLL's, how do I go about doing it?

This is a continuation of this question . I'm in the process of testing whether rebasing the .NET DLLs, and NGENning them will provide me with more shared code in memory on terminal servers. However, my plan seems to have a flaw, and it's that I seem unable to find a working method to figure out a working set of addresses. What I thought I could do was as follows: Just build and NGEN everything Start the program, ensuring all the DLL's have been loaded Use LISTDLLS /R PROGRAMNAME to get a list of current in-use addresses for the running instance Use the addresses of those DLL's that was