E
Emby
I was wondering if anyone specifies a base loading address for .NET
Libraries (DLL projects). This can be done on the Advanced Compiler Settings
dialog, accessed from the Compile page of Project properties in VB.NET 2005
projects.
The default is &H11000000, so if you have several DLLs loading, they will
all try to load at that address. The first may succeed, but all others will
fail, and, as I understand it, the loader will have to rebase the dll
on-the-fly (at least that's how it used to work ;-)
The down side is a slower load (no app needs that), and traditionally, it
can also be harder to debug in the event of a crash. Also, is there the
equivalent of a "map file" for .NET apps? Or is that obsolete with the event
of JIT compilation?
I really don't know how much of this "old experience" applies to .NET apps -
can anyone straighten me out?
Thanks
Libraries (DLL projects). This can be done on the Advanced Compiler Settings
dialog, accessed from the Compile page of Project properties in VB.NET 2005
projects.
The default is &H11000000, so if you have several DLLs loading, they will
all try to load at that address. The first may succeed, but all others will
fail, and, as I understand it, the loader will have to rebase the dll
on-the-fly (at least that's how it used to work ;-)
The down side is a slower load (no app needs that), and traditionally, it
can also be harder to debug in the event of a crash. Also, is there the
equivalent of a "map file" for .NET apps? Or is that obsolete with the event
of JIT compilation?
I really don't know how much of this "old experience" applies to .NET apps -
can anyone straighten me out?
Thanks