Why .net requires .dll file ?

[montu3377]

Hi, Here i am facing one problem in making .exe file,whole situation is like below. My main project is in C#.net and i had made .dll file from that,now client requirement is that,he wants to run the .exe file of our project from vb 6.0 but that must be console application so i had made .dll file from my project and one another .net project include that .dll and then i made .Exe file of that project which is .net console application,it means that my second project is includes .dll of my project and now for testing purpose i had made third project which include second projects only .exe file but now problem is that third project also required first projects .dll otherwise it is not working. Here is 3 project's outputs and included files. first project : out of that made .dll file. second project : made console application and include first project's .dll file and then made .exe file Third project (for testing) :if i include only second project's .exe then project is not working and if i include second project's .exe and .dll both if working fine. Now my question is that why my third project required .dll of second project,actually third project should not required .dll file ,only .exe of second project is enough. hope you not confused with all of above. if any query regarding understanding pls ask me.

[S Senthil Kumar]

Perhaps a little more punctuation would help? From what I understood, you have 2 executables and a dll. One of the executables is linked to that dll, the other only uses the first executable. If you are asking why the dll is needed, you haven't understood dynamic linking. DLL (dynamic linked library) means that linking (resolving method names to addressed) takes place when the executable is loaded into memory. Which obviously means that the dll has to be available when the executable is loaded. Does this make sense? Regards Senthil _____________________________ My Blog | My Articles | WinMacro