Error on Load mytest.dll at runntime

Question

0.00/5 (No votes)

See more:

Hi,

In my csharp application when i tried to load a dll called mytest.dll by using

Assembly a = Assembly.LoadFrom("mytest.dll");

It show an error like

Could not load file or assembly 'file:///C:\Users\DEVP\Documents\Visual Studio 2008\Projects\ConsoleApplication1\ConsoleApplication1\bin\Release\mytest.dll' or one of its dependencies. The system cannot find the file specified.

i copied mytest.dll to C:\Users\DEVP\Documents\Visual Studio 2008\Projects\ConsoleApplication1\ConsoleApplication1\bin\Release\

also...

Posted 11-Sep-13 22:24pm

rose lindo

Add a Solution

Comments

CPallini 12-Sep-13 4:40am

"or one of its dependencies" might be the key.
Did you write the DLL on the same machine?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-09-12T06:43:00

The exception (not error!) is self-explaining. You should make sure than the DLL in question is placed to the output directory of the project containing the code loading it. Alternative solution would be providing the "app.config" file which can be used to provide a "hint" path where this DLL can be found during runtime (if you are interested, I'll give you the information on this technique, just ask me a follow-up question, but this is not the main approach, but it has limited applicability).

If "mytest.dll" is build by your project, the best way to deal with that would be putting the this project in one solution with the project containing the code loading it. Then, if assemblies are dependent statically, you normally add references to the projects, not assemblies, by using the tab "Projects" of the "Add Reference" window. It won't help if you load "mytest.dll" dynamically, during runtime. So, it would be the best if you modify all your products to have output directories (separate for each Configuration or Configuration/Platform combination) in the same directory. For example, I usually use the paths like "..\..\..\bin.Debug" or "..\..\..\bin.Release" and write the number of "..\" the way all projects get the same physical output directories, somewhere on some directory parent to all project directories.

This is actually the best solution configuration even if you never use dynamic DLL loading. You see, by default, Visual Studio creates separate output directories, but output of the dependency projects is copied to dependent project's output; this creates multiple copies of executable modules and other things, which is somewhat wasteful. Visual Studio does it just to provide its "works immediately" quality, but it is not the best for well-tuned solution.

—SA