Arne Janning,
still not working.. but i'm sure ur method work fine.. i just don't know
which part i did wrong
let me tell u my structure in detail
C:\AppFolder <== this is the application folder which contains Main.EXE
(executable file) and Main.EXE.Config
that is:- C:\AppFolder\Main.EXE
C:\AppFolder\Main.EXE.Config
C:\AppFolder\System <== this folder contain all the dll reference files
including some dll files that Main.EXE referenced
that is:- C:\AppFolder\System\Kernel.Database
C:\AppFolder\System\Kernel.Global
Main.EXE.Config
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<runtime>
<asm:assemblyBinding>
<asm:probing privatePath="System" />
</asm:assemblyBinding>
</runtime>
</configuration>
do u know where i make the mistake??
does it make any problem if Main.EXE contain reference to Kernel.Global ???
Many thanks,
Ivan
"Arne Janning" <sp*****************@msn.com> ???
news:e%****************@tk2msftngp13.phx.gbl ???...
Ivan wrote: First of all, Thanks for ur reply
so i have to creat a configuration file which is the same name as my
startup executable file
like MIR.exe with MIR.exe.config with the following code
<?xml version="1.0" encoding="utf-8" ?>
<configuration xmlns:asm="urn:schemas-microsoft-com:asm.v1">
<runtime>
<asm:assemblyBinding>
<asm:probing privatePath="System;sPortal" />
</asm:assemblyBinding>
</runtime>
</configuration>
BUT one problem.. i put the configuration file in the same project with
MIR.exe but it seems not built..
i can't find the output file and it is not working...
did i do something wrong ??.. and what should i do to make it work??
Hi Ivan,
MIR.exe.config does not have to be "built". Simply copy the
MIR.exe.config into the _same_ directory where your MIR.exe is.
With the example you provided the CLR loader will search your dll in
these directories:
APPDIR\yourdll.dll
APPDIR\yourdll\yourdll.dll
APPDIR\System\yourdll.dll
APPDIR\System\yourdll\yourdll.dll
APPDIR\sPortal\yourdll.dll
APPDIR\sPortal\yourdll\yourdll.dll
If your dll is culture-dependent (e.g. "en-US") then the CLR loader will
search in these directories:
APPDIR\en-US\yourdll.dll
APPDIR\yourdll\en-US\yourdll.dll
APPDIR\System\en-US\yourdll.dll
APPDIR\System\yourdll\en-US\yourdll.dll
APPDIR\sPortal\en-US\yourdll.dll
APPDIR\sPortal\yourdll\en-US\yourdll.dll
Is your dll located in one of these directories? If so it should work.
Cheers
Arne Janning