Why C# library cannot be found in system32 folder?

Question

Project has a reference to lib. If this lib lays near the executable, all works fine. But I need to put this lib to System32 folder. But in this case project fails, raising filenotfoundexception.

I thought that I can feel myself free to put my libs to system32 folder without any harm for my app.

What's wrong with all this?

*Why* do you need to put it in the System32 folder? If you need it globally, why not put it in the GAC? — Jon Skeet, Mar 01 '12 at 11:31
possible duplicate of [Resolve assembly references from another folder](http://stackoverflow.com/questions/5260404/resolve-assembly-references-from-another-folder) — MattDavey, Mar 01 '12 at 11:32
I cannot use my library in the application folder or its subfolder and I thought that simpliest way to use it is to place it to system32 folder.\ — yurart, Mar 01 '12 at 11:40
Application and lib are different projects and must be located in different folders. It is a requirement. — yurart, Mar 01 '12 at 11:55

score 4 · Answer 1 · answered Mar 01 '12 at 11:32

4

The .NET runtime doesn't probe for custom DLLs in system32. This article explains how assembly loading and probing works:

http://msdn.microsoft.com/en-us/library/yx7xezcf(v=vs.90).aspx

answered Mar 01 '12 at 11:32

TarkaDaal

18,798
7
34
51

Thank you! I think I understand how it works now.in my case the only way is GAC – yurart Mar 01 '12 at 11:37

score 2 · Answer 2 · answered Mar 01 '12 at 11:31

2

If it's a managed assembly, you need to put it into GAC instead (and that requires strong name).

answered Mar 01 '12 at 11:31

wRAR

25,009
4
84
97

Yes, it is really good advice. I already solved my problem with the help of GAC. – yurart Mar 02 '12 at 10:25

Why C# library cannot be found in system32 folder?

2 Answers2