microsoft / brokered-winrt-components

This repo contains samples demonstrating an enterprise-targeted feature supported by Windows 10 that allows UWP apps to use existing legacy code responsible for key business-critical operations.

Brokered Windows Runtime Components for a side-loaded UWP app

This sample demonstrates an enterprise-targeted feature for Windows 10 that allows UWP apps to use existing legacy code responsible for key business-critical operations. The samples shows an example of Brokered Windows Runtime Components and their Proxy Stubs, enabling a side loaded UWP app to communicate with pre-existing desktop components. For more info see the documentation page.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

brokered-winrt-components's Issues

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

How to broke WinRT component between two different app containers?

There a way to make brokered WinRT component to Win32 application, but application manifest allows to declare OutOfProcessServer in this way:

<Extension Category="windows.activatableClass.outOfProcessServer">
    <OutOfProcessServer ServerName="ExtensionsTests" uap5:IdentityType="activateAsPackage" uap5:RunFullTrust="false">
      <Path>Extension0.WinRTServer.exe</Path>
      <Instancing>singleInstance</Instancing>
      <ActivatableClass ActivatableClassId="winmd.TestClass" />
    </OutOfProcessServer>
  </Extension>

So, how to serve WinRT component between two application containers? I want to escape defining runFullTrust capability and make extensible apllication by brokered WinRT components.

Doesn't build

BrokeredComponent project fails to build:

> 1>MDMERGE : error MDM2006: C:\src\practice\Brokered-WinRT-Components-master\Brokered-WinRT-Components-master\Samples\Visual Studio 2017\BrokeredComponent - Server\BrokeredComponent\bin\Debug\Fabrikam.winmd does not appear to be a valid Windows Runtime metadata file
> 1>MDMERGE : error MDM2005: Unable to open metadata file C:\src\practice\Brokered-WinRT-Components-master\Brokered-WinRT-Components-master\Samples\Visual Studio 2017\BrokeredComponent - Server\BrokeredComponent\bin\Debug\Fabrikam.winmd.

VS 2017 info:

Microsoft Visual Studio Community 2017
Version 15.5.3
VisualStudio.15.Release/15.5.3+27130.2020
Microsoft .NET Framework
Version 4.7.02556
Installed Version: Community
Visual C# 2017 00369-60000-00001-AA838
Microsoft Visual C# 2017
Visual C++ 2017 00369-60000-00001-AA838
Microsoft Visual C++ 2017

Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package

NuGet Package Manager 4.5.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

Visual Studio Tools for Universal Windows Apps 15.0.27130.2020
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.