You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Sergey Shakhnazarov (JIRA)" <ji...@apache.org> on 2016/10/27 14:15:58 UTC

[jira] [Commented] (CB-12071) Fix for CB-11825 breaks usage of InProcessServer in Cordova Windows

    [ https://issues.apache.org/jira/browse/CB-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612020#comment-15612020 ] 

Sergey Shakhnazarov commented on CB-12071:
------------------------------------------

[~lhm], thanks for reporting the issue!
Could you please describe your scenario - what is InProcessServer used for?
I can't find any resources/articles on this topic.
Also - was the deploy working for you for 8.1 Phone/10 Mobile previously with PackageAction=None?

As a workaround for now I can see opening a dll Properties in Visual Studio and switching back to Content Package Action.

> 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="&gt;=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: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org