Forum Discussion
Flat directory structure for WPF application packaged into MSIX
Hi, I have a WPF application packaged into a MSIX using the "Windows Application Packaging" template project, and other cpp dll files used by that project. Everything is building fine, BUT the re...
Not directly answering the request on getting VS to provide the structure you wanted, but...
You can add https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap6-loadersearchpathoverride to the manifest to tell dll loading to search for an additional folder. There is also an API call that the app can make, but uap6:LoaderSearchPathOverride is easier as you can define the path as relative to the package root folder.
You can add https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap6-loadersearchpathoverride to the manifest to tell dll loading to search for an additional folder. There is also an API call that the app can make, but uap6:LoaderSearchPathOverride is easier as you can define the path as relative to the package root folder.
Thank you for you answer, that could definitely help.
I also found another workaround, I am now only referencing the WPF project in the MSIX packaging project, and in the WPF project I am adding my other DLLs using 'Add existing Item', 'Add as link' (dropdown on 'Add', it is a bit hidden). Then 'Copy if newer' in the item properties.
That way the dll are copied into the WPF project output directory automatically when building it, and the packaging project put everything into the WPF subfolder.
This is still not entirely flat, I still have the WPF subfolder, but I have no relative paths for DllImport anymore.
Using your solution on top of that could also help.
I also found another workaround, I am now only referencing the WPF project in the MSIX packaging project, and in the WPF project I am adding my other DLLs using 'Add existing Item', 'Add as link' (dropdown on 'Add', it is a bit hidden). Then 'Copy if newer' in the item properties.
That way the dll are copied into the WPF project output directory automatically when building it, and the packaging project put everything into the WPF subfolder.
This is still not entirely flat, I still have the WPF subfolder, but I have no relative paths for DllImport anymore.
Using your solution on top of that could also help.