-
Notifications
You must be signed in to change notification settings - Fork 271
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
package-level extension #59
Comments
Hi Hongtao,
The package-level extension gets written automatically by VS during the build process, so you typically don’t need to worry about. If you look for the appxmanifest.xml in the build output you should be able to view the extension added for you automatically.
Let me know if this doesn’t answer your question.
Thanks,
Stefan
From: Hongtao Chen [mailto:[email protected]]
Sent: Monday, February 12, 2018 5:52 PM
To: Microsoft/DesktopBridgeToUWP-Samples <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [Microsoft/DesktopBridgeToUWP-Samples] package-level extension (#59)
In the WinformAppService example, the README.MD mentioned that:
"This component gets activated out-of-proc to the main application process, so we also need to declare a package-level extension to explain to the system how the class will get activated."
But I can find more detail about the package level extension.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FDesktopBridgeToUWP-Samples%2Fissues%2F59&data=04%7C01%7Cswick%40microsoft.com%7C294fba80e2c34c8418c208d572845fae%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636540835224681415%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=0GJo5MtA%2FCTQod8Z29z0Uwj5NKu4s75dAqFA2WSXWT0%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASRavBLYuWekO9XPstEXM2SUGK7Xt3vfks5tUOrAgaJpZM4SDGcg&data=04%7C01%7Cswick%40microsoft.com%7C294fba80e2c34c8418c208d572845fae%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636540835224681415%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=U7r068AvAvUiKmww4wuJSGNcKXIIupdo%2FkD72zVSLd8%3D&reserved=0>.
|
It's not there. I tried to follow the Win Form App Service, but, in appx manifest xml, no package level extension created for my runtime component. |
I just tried it and it works for me. Here is how I tested:
1. Build the solution
2. Right-click on the “TestClient” project and select deploy
3. Go to \WinformsAppService\x64\Debug\TestClient\AppX folder
4. Inspect the created appxmanifest file
There you will find the package-level extension created as:
<Extensions>
<Extension Category="windows.activatableClass.inProcessServer">
<InProcessServer>
<Path>AppServiceComponent.dll</Path>
<ActivatableClass ActivatableClassId="AppServiceComponent.MyAppService" ThreadingModel="both" />
</InProcessServer>
</Extension>
</Extensions>
From: Hongtao Chen [mailto:[email protected]]
Sent: Tuesday, February 13, 2018 9:54 PM
To: Microsoft/DesktopBridgeToUWP-Samples <[email protected]>
Cc: Stefan Wick <[email protected]>; Comment <[email protected]>
Subject: Re: [Microsoft/DesktopBridgeToUWP-Samples] package-level extension (#59)
It's not there. I tried to follow the Win Form App Service, but no package level extension created for my runtime component.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FDesktopBridgeToUWP-Samples%2Fissues%2F59%23issuecomment-365504053&data=04%7C01%7Cswick%40microsoft.com%7C52df67612f3d424dddd908d5736f6015%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636541844629049065%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=gjYrxskSPlLCeD%2BeRcPX78%2BrmV7DgNZRs6nVsOmxla0%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASRavCTDsfzj3lfB_Oqz7JAcIYFKl6l-ks5tUnUEgaJpZM4SDGcg&data=04%7C01%7Cswick%40microsoft.com%7C52df67612f3d424dddd908d5736f6015%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636541844629049065%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=PSMq47uJf518OslqvbHIwvyIII24uuzJvWlnwNL2NsY%3D&reserved=0>.
|
Thanks a lot, I put my POC in the one drive. https://1drv.ms/u/s!Ar4lO2gIHPQZsz3j2HTXbioHFFBq I can build and deploy it. But no package level extension created in manifest xml, and when the win form app tries to connect to the app service. it fails with app unavailable. |
Thanks a lot, that helps. Now I see the extension session in the generated manifest xml file. But when the winform UI try to connect to it, I still get App unavailable error. Is there something I still missed? |
The UI is the winform app still, I try to use it to connect to some features that converted to UWP runtime already. The Cpp project there is just a package project for now, business logic will be in the C# library. Because the project designed in the way that the winform app and UWP communicate with app service only, I cannot call the library directly from the winform app. |
Still blocked by the application is not available problem, any idea? |
Here is the updated example: https://1drv.ms/u/s!Ar4lO2gIHPQZs0474Vn6MRKoSYy- When I click the button, I still get the service unavailable error. Thanks, |
In the WinformAppService example, the README.MD mentioned that:
But I can't find more detail about the package level extension.
Also notice that the vcxproj file missing the Package.StoreAssociation.xml, is that related?
The text was updated successfully, but these errors were encountered: