com - Why/when TypeLib should be registered? -

com - Why/when TypeLib should be registered? -

this think know:

typelib descripes "what should out there" (=how locate , phone call actual class) if .tlb -file (=typelib) imported in c++ -code @ compile time, compiled code contains info "what should out there". interop -assembly (.net) pretty much same .tlb -file. it's in assembly-form .net code can compiled against it, contains info "what should out there". if interop in embedded, typelib-info included in assembly , there's no need deploy separate interop-dll when application deployed. if interop not embedded, interop-dll must deployed same folder calling assembly info can found caller.

of course of study actual classes typelib pointing must registered can found depth of machine tybelib-info.

please right me, if above wrong.

my question is, based on above "knowledge", why see articles/questions/tutorials registering typelibs? doesn't create sense me (yet), since registering them shouldn't provide excess info caller.

thank you.

com registry interop com-interop typelib