Hi Andres,
You have to be quite careful when changing COM interfaces - the COM rules specify that a published COM interface can never change, and Excel might use this fact in its internal caching of information from your references. Using explicit interfaces instead
of AutoDual as the class interface can help a bit with this.
From your example it seems like you would need both type libraries to describe your COM server, since the WebQuote class has a method that returns a type from MyClassLibrary. I'm not sure why you're surprised that you need both - how else would Excel know
what a LibQuote is?
I don't know anything about how TlbExp deals with dependencies - the code is somewhere on the web, though. But it seems safest to always regenerate all the type libraries you need, or perhaps to make a single library that contains all the COM interfaces
you'll use from VBA.
Excel-DNA has a packing feature that will put the .tlb file into the .xll file, and then you can reference the .xll file directly from the VBA Tools->References. This helps you distribute only a single file for your add-in, but won't make any difference
in the above issues of versioning COM interfaces or what Tlbexp generates.
Another option is to make everything late-bound from VBA, then you don't need to Tools->Reference anything, but you lose IntelliSense, compile-time error checking etc. I presume that's where you starting when trying out the Excel-DNA COM Server features.
-Govert