Thank you Rob. Hmm from your samples/templates it seems we can only write Brokered Runtime Components using C#? This would not be an option, since my app is a JS/HTML one and dragging in the .Net runtime I would like to avoid. Technically it should be possible
to write a Brokered Component in C++ as I understand in the end its COM under the hood.
I see in the manifest of the client app:
<Extension Category="windows.activatableClass.inProcessServer">
<InProcessServer>
<Path>clrhost.dll</Path>
<ActivatableClass ActivatableClassId="Fabrikam.EnterpriseServer" ThreadingModel="both">
<ActivatableClassAttribute Name="DesktopApplicationPath" Type="string" Value="c:\test" />
</ActivatableClass>
</InProcessServer>
</Extension>
Does that mean the Brokered Component could also be in an out-of-proc server? That would make debugging a lot easier, since I can simply set a breakpoint in the servers code.