Github user biasmv commented on the pull request:
https://github.com/apache/cordova-windows/pull/139#issuecomment-174499126
@sgrebnov: I've verified that it's still possible to have files in non-root
folder locations. I've inserted the following into my project (which is
essentially what would be generated by resource-file with the patch):
```
<Content Include="file.txt">
<Link>somesubdirectory/file.txt</Link>
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Content>
```
The file is correctly placed in somesubdirectory and not the output
directory root folder. So the patch does not prevent the resource element to be
used that way.
The suggested use of the target attribute would still mean that the files
land in different locations depending on the architecture. I'd need to change
the C# library to somehow load the unmanaged dll from from a different
location, depending on what device it's running on. I'd prefer if I could just
copy the file with the correct architecture to the output directory without
having to do any runtime checks.
Also, since I'm referencing the file from the appxmanifest as part of an
extension (see the original ticket
https://issues.apache.org/jira/browse/CB-10326), I'd need to change the path in
the appxmanifest depending on the architecture currently being built.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
