[
https://issues.apache.org/jira/browse/CB-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15614816#comment-15614816
]
Luc Humair commented on CB-12071:
---------------------------------
Our scenario requires us to use
[MediaCapture.AddEffectAsync|https://msdn.microsoft.com/en-us/library/windows/apps/br211961.aspx]
which needs an activatable runtime class. This
[ActivatableClass|https://msdn.microsoft.com/en-us/library/windows/apps/dn934736.aspx]
is declared using an InProcessServer.
The deployment with version 4.4.2 and manually setting PackageAction=None does
not work either (the build fails with the same error).
Currently, we tell our customers to use version 4.4.2 as a workaround. With
version 4.4.3 I can also only see the workaround of manually switching the
PackageAction.
Btw: I played around with the sample provided with issue CB-11825. Suprisingly
the deployment succeeds if I move the DLL to the project's root folder (while
still having the PackageAction=Content property). Specifically I changed part
of the file CordovaApp.projitems from:
{code:xml}
<ItemGroup>
<Content
Include="$(ProjectDir)..\..\plugins\com.plugin.test.myPlugin\windows\windows10\bin\SayHelloLib.dll">
<Link>plugins/com.plugin.test.myPlugin/SayHelloLib.dll</Link>
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
</ItemGroup>
{code}
to
{code:xml}
<ItemGroup>
<Content
Include="$(ProjectDir)..\..\plugins\com.plugin.test.myPlugin\windows\windows10\bin\SayHelloLib.dll">
<Link>SayHelloLib.dll</Link>
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
</ItemGroup>
{code}
This matches the configuration we also use in our project. As the deployment
succeeds this way, I am wondering whether the patch for CB-11825 actually fixed
a problem or rather a symptom of some other problem.
> Fix for CB-11825 breaks usage of InProcessServer in Cordova Windows
> -------------------------------------------------------------------
>
> Key: CB-12071
> URL: https://issues.apache.org/jira/browse/CB-12071
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugins, Windows
> Affects Versions: 4.4.3
> Environment: Windows Phone 8.1, Windows 8.1, Windows 10 UWP
> Reporter: Luc Humair
> Priority: Critical
>
> I have a plugin which needs an InProcessServerExtension in the project's
> package.windows.appxmanifest like:
> {code:xml}
> <Extensions>
> <Extension Category="windows.activatableClass.inProcessServer">
> <InProcessServer>
> <Path>Foo.dll</Path>
> <ActivatableClass ActivatableClassId="Foo.Class"
> ThreadingModel="both" />
> </InProcessServer>
> </Extension>
> </Extensions>
> {code}
> The corresponding DLL is configured in the plugin.xml file using:
> {code:xml}
> <resource-file device-target="windows"
> src="src/windows/win81/$(Platform)/Foo.dll" target="Foo.dll" versions="8.1"/>
> <resource-file device-target="phone"
> src="src/windows/wpa81/$(Platform)/Foo.dll" target="Foo.dll" versions="8.1"/>
> <resource-file src="src/windows/uap/$(Platform)/Foo.dll" target="Foo.dll"
> versions=">=10"/>
> {code}
> This configuration worked until release 4.4.2. Foo.dll was included in the
> projects with property "Package Action"="Content" which includes the DLL in
> the package manifest.
> Release 4.4.3 introduced a patch related to issue CB-11825 that changes the
> DLL's "Package Action" to "None". Now the file is no longer included in the
> package manifest and the build fails for all the platforms with the following
> error message:
> package.windows.appxmanifest : error APPX0703: Manifest references file
> 'Foo.dll' which is not part of the payload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
