how dlls link together

[DebbieInFlorida]

This is going to sound lame, but I could use some simple clarification. I am working on a project that has about 5 dlls involved. The main one is the Toolbar, it calls A or C, A call B, B call D. etc I was under the impression that DLLs, once compiled and registered were available as is. But I find that if I make a change in a lower DLL, ie B, then I have to recompile, A, then recompile Toolbar, in that order or the latest change won't be taken, actually I will get an error. Is this normal, seems like a lot of work every change. Also, when I deliver this application, what is the best way to do that, since I have about 5 DLLs under the main one. Thanks for patience..

[Merrion]

Are you talking about ActiveX dlls?

If so, you need to make sure that they use the same GUID when you recompile them. IN VB6 you do this by checking the "Binary compatibility" box in the compile options.

[ComputerJy]

If you are talking about .NET dlls, put them in the same solution/workspace and rebuild the entire solution when changing anything

[DebbieInFlorida]

I should have clarified, I am using Vb6 activex dlls. Sorry for being so vague.