Attaching to an already running Office application from your application using GetActiveObject or BindToMoniker

One common pattern of Office development is the Office Automation Executable—a console or windows forms application that starts up an Office application and talks to it.  Sometimes you won’t want to start a new instance of an Office application but will instead want to attach to an already running instance. To do this, you can use one of two methods provided by .NET. System.Runtime.InteropServices.Marshal.GetActiveObject allows you to attach to a running instance of an Office application by passing a string identifier for the Office application called a program ID or ProgID

Excerpt from:
Attaching to an already running Office application from your application using GetActiveObject or BindToMoniker

Sharing Custom Tabs in The Ribbon UI

To let add-ins (native, unmanaged/managed COM add-ins and VSTO add-ins) share tabs is a good strategy but it can be applied in two different ways. Which to apply is depended on the individual add-ins. Sharing the Add-ins Tab For small application it is not necessary to use tabs on their own

Original post: 
Sharing Custom Tabs in The Ribbon UI