diff --git a/Samples/PackagedOleDocument/Readme.md b/Samples/PackagedOleDocument/Readme.md index 115414ee..dde71fa8 100644 --- a/Samples/PackagedOleDocument/Readme.md +++ b/Samples/PackagedOleDocument/Readme.md @@ -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 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 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 -------------------------------