On Thu, 21 Jun 2007 09:44:55 -0700, Curt Hagenlocher <[EMAIL PROTECTED]>
wrote:
>There's no "standard place" to store "plain
>old" DLLs such that the operating system or CLR can find the right DLL.
Actually, there is at least one such place, as I said in my original post:
%windir%\system32 and %w
On 6/21/07, Ron Inbar <[EMAIL PROTECTED]> wrote:
But there's no logic, except that 32-bit processes should load 32-bit
DLLs,
and 64-bit processes should load 64-bit DLLs. I don't see any reason why
this logic should be in my code and not in the OS or the CLR.
If only your code knows where t
;To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
>Subject: [ADVANCED-DOTNET] Loading 32/64-bit unmanaged DLLs
>
>Hi,
>
>I want to compile my managed assemblies (both DLLs and EXEs) as AnyCPU.
>I have a small number of unmanaged DLLs, for some of which I have both a
>32-bit version and a
NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Ron Inbar
Sent: Tuesday, June 19, 2007 3:39 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Loading 32/64-bit unmanaged DLLs
Hi,
I want to compile my managed assemblies (both DLLs and EXEs) as AnyCPU.
I have a small number of unma
Hi,
I want to compile my managed assemblies (both DLLs and EXEs) as AnyCPU.
I have a small number of unmanaged DLLs, for some of which I have both a
32-bit version and a 64-bit version, and for others I only have a 32-bit
version.
Obviously, applications that load DLLs of the latter kind must be c