Could not load assembly

Question

I have a normal winforms app. I run it and it calls some logic in another .dll (another project part of the solution). I get an error (my own exception) saying could not load assembly etc etc.

I've used the assembly log viewer but could not find an issue - all I found was that the windows service the program uses was installed/deployed on another account. My winforms app calls this service, which in turn calls logic in its own and different .dlls.

Could this be an issue? Thanks

alexD · Accepted Answer · 2011-07-21 18:41:16Z

1

If you use a FileDialog and open/save/write a file to another directory other than the one that contains your exe/dlls, it will change the programs working directory if you do not set the FileDialog.RestoreDirectory = true. This one caused me fits for a while, and would explain why it appears intermittent.

answered Jul 21, 2011 at 18:41

alexD

2,3742 gold badges32 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Ben Voigt Over a year ago

This is the most likely cause of an "intermittent" failure. Of course, looking for DLLs in the working directory is a bad idea to begin with.

blade33 Over a year ago

How/where do I set that value?

alexD Over a year ago

RestoreDirectory is a property of FileDialogs. For example, if you are using an OpenFileDialog called ofd, just set ofd.RestoreDirectory = true. The would apply for a SaveFileDialog as well.

blade33 Over a year ago

I don't use that. Just call various classes etc.

Tigran · Accepted Answer · 2011-07-21 18:20:18Z

Check your project .NET Framework version, and your assembly .NET Framework version, problem could be there.

Regards.

Yuck · Accepted Answer · 2011-07-21 18:21:38Z

Make sure the assembly it's looking for is in the same directory that you're running the application from, or that it's registered in the GAC (Global Assembly Cache) - and that it's the correct version.

JGWeissman · Accepted Answer · 2011-07-21 18:24:03Z

0

Make sure your application and all its dependencies are either all 32 bit or all 64 bit assemblies.

answered Jul 21, 2011 at 18:24

JGWeissman

7286 silver badges19 bronze badges

4 Comments

blade33 Over a year ago

How do I do that? This problem is intermittent btw.

Ben Voigt Over a year ago

@blade33: Bitness isn't intermittent, so this is probably not the problem in your case. Run dumpbin /headers and dumpbin /clrheader on a .DLL or .EXE to find out the platform.

JGWeissman Over a year ago

You can also check the configuration manager in Visual Studios, which is where you would fix it if it is wrong (and then recompile).

JGWeissman Over a year ago

By intermittent, do you mean that it sometimes successfully loads the problem assembly (if so I agree with Ben, bitness is not the problem), or is it possible you your application only sometimes tries to load the promblem assembly?

Collectives™ on Stack Overflow

Could not load assembly

4 Answers 4

4 Comments

Comments

Comments

4 Comments

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

4 Comments

Comments

Comments

4 Comments

Related