> "When a component is configured to use COM+, it must reside in only
> one COM+ application."
>
> I'm having trouble interpreting this. They cannot be stating that a
> component can only be used by a single COM+ application. What are they
> saying?

"Tomas Restrepo \(MVP\)" <tomasr@mvps.org> wrote in message news:<OhFzzqviEHA.2848@TK2MSFTNGP10.phx.gbl>...

> A COM+ component can only be registered in one application [1]. This
> includes .NET ServicedComponents. The thing is: You can *use* it (call it)
> from other applications, but the component itself can only be registered in
> the COM+ catalog inside a single COM+ application.
>
>
> [1] This changes a little with partitions in Windows Server 2003, but the
> essence is the same....

> I can use Component Services on XP Pro to create two COM+ applications
> and add the same component (ATL DLL) to each. Doesn't this contradict?

"Tomas Restrepo \(MVP\)" <tomasr@mvps.org> wrote in message news:<eqdjpq8iEHA.4044@tk2msftngp13.phx.gbl>...
> Hi John,
>
> > I can use Component Services on XP Pro to create two COM+ applications
> > and add the same component (ATL DLL) to each. Doesn't this contradict?
>
> That won't do what you expect it to do, though...
>
> Just try this: Check on which of the two applications your component is
> getting activated....