Trying to understand VS AddIns

[dburns]

Hi, I'm coming up to speed on C++ AddIns (I plan to write one). Having played with a lot of samples, I think I've got a handle on the basic architecture. I see that it's common to have TWO dlls registered for a given AddIn -- one that seems to be just a bootstrap that tells VS about the other one (the projects are typically called MyAddin and MyAddinControl). I see it's quite possible to do it all in a single dll, and in fact that's the framework provided by the VS wizard when you create an AddIn. So I'm wondering why people seem to like to split it in two pieces? Is there some advantage to doing that? Thanks! DB