Command Line Complier + subdirectory dll not working

Alas , i have figured it out ,  quite possibly it  was  just typos inside my config script

app.exe is inside application folder ...  testa.dll and testb.dll are inside the DLL folder and program is now runnin on its own.

 

Thanks for pointing the direction once more :P

Question answered, Topic closed  Big Grin.

Ahah!. Yes you are correct , i have now read all the MSDN info on the CLR , but , i am still not sure what im doing with this config file.

 

I wrote a config file and when i launched the exe , it said there was an error in the  config file itself .....

 

  
     
        
     
  

 

this is my current config file.  Am i supposed to write anything with my app source code to make this happen?

Im sorry if i sound like a blundering idiot , but i have never had to use a config file , and i never had a reason to keep my dll's in a subdirectory before. But with this project , theres a lot of custom made dll's and its just a real big mess having them all in the main app folder.

Now as i said , i read over most everything  @ MSDN , but at best , im still totally confused on how to write and set up my app, app.config and dll's.

 

Thanks for sending me in the right direction though :D.

The problem here is that the CLR doesn't use the same rules to find assemblies as the compiler does.

There's a mention of this in the MSDN reference for the /lib compiler switch which in turn links to an article entitled "How the Runtime Locates Assemblies":

http://msdn.microsoft.com/en-us/library/s5bac5fx(VS.80).aspx

However, the following article is a bit more readable:

http://kalpeshshirodker.wordpress.com/2007/09/06/specify-where-to-look-for-referenced-assemblies-in-c-application/

Personally, I can't be bothered with the application configuration file and so always copy my private dlls to the application folder.

Hmm, just a guess here; is /lib:DLL sufficient? Does /lib:.\DLL make a difference (specifying the absolute path)?