Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Readme.md #121

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Samples/PackagedOleDocument/Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This sample demonstrates how to publish support for Ole Documents in an applicat

AppxManifest
------------
To understand how the UWP and Desktop Bridge enables this scenario, let's look at the relevant lines in the [AppxManifest.xml] (https://github.com/Microsoft/DesktopBridgeToUWP-Samples/blob/master/PackagedOleDocument/PackageFiles/AppManifest.xml) file. The entry point is the Scribble application that we have converted using the Desktop App Converter. Now we can add Packaged Ole support through the <windows.comServer> extensions. These manifest extension registrations are very similar to the existing registry entries. When the application is installed, this information is registered with COM in a private catalog and is managed by the system. When a clients attempts to embed a document, the system is able to look in both the Packaged Com catalog and the system registry in order to find and activate the Ole server.
To understand how the UWP and Desktop Bridge enables this scenario, let's look at the relevant lines in the [AppxManifest.xml](https://github.com/Microsoft/DesktopBridgeToUWP-Samples/blob/master/PackagedOleDocument/PackageFiles/AppxManifest.xml) file. The entry point is the Scribble application that we have converted using the Desktop App Converter. Now we can add Packaged Ole support through the <windows.comServer> extensions. These manifest extension registrations are very similar to the existing registry entries. When the application is installed, this information is registered with COM in a private catalog and is managed by the system. When a clients attempts to embed a document, the system is able to look in both the Packaged Com catalog and the system registry in order to find and activate the Ole server.

Build/Deploy and Run the sample
-------------------------------
Expand Down