DLL reference not found when changing the app path
-
Hi, i'm having this problem and can't find a solution. This image describes all the problem.(Image) Thanks a lot.
-
Hi, i'm having this problem and can't find a solution. This image describes all the problem.(Image) Thanks a lot.
-
Hi, i'm having this problem and can't find a solution. This image describes all the problem.(Image) Thanks a lot.
There are only two places the dll will be searched if you have added them as reference 1. Current working directory 2. C:\windows\system32 (till XP). You can place your dlls in any of these places. Otherwise it won't get loaded
-
There are only two places the dll will be searched if you have added them as reference 1. Current working directory 2. C:\windows\system32 (till XP). You can place your dlls in any of these places. Otherwise it won't get loaded
-
Shameel wrote:
Have you ever heard of anything called assembly probing ?
No
-
Shameel wrote:
Have you ever heard of anything called assembly probing ?
No
You can actually instruct Fusion (the assembly resolution subsystem of CLR) to check subfolders (in your app's folder) for referenced assemblies. This has to be done in the application's config file. You can even compile referenced assemblies as embedded resources in your app and dynamically extract them and provide it to Fusion. For an example of this, visit www.albahari.com
-
You can actually instruct Fusion (the assembly resolution subsystem of CLR) to check subfolders (in your app's folder) for referenced assemblies. This has to be done in the application's config file. You can even compile referenced assemblies as embedded resources in your app and dynamically extract them and provide it to Fusion. For an example of this, visit www.albahari.com
Didn't know that. Thank you very much for that.
