User Profile
LordOfDragons
Copper Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Package dependency on non-framework package
I've been send over from https://docs.microsoft.com/en-us/answers/questions/657816/wack-does-not-allow-creating-framework-packages.html?childToView=659087#comment-659087. I need 3 packages to be deployed, where the first two can be argued to be combined into one if necessary. The first package is a framework package with only DLLs and runtime environment. I could not get this uploaded because it seems I'm not allowed to create framework packages (tag framework not allowed). The second and third depend on the first needing the DLLs and runtime environment to be present in their VFS. But MSIX did not allow me to depend on the first package if I did not declare it as framework. But since I'm not allowed to create a framework package, how am I supposed to create this kind of dependency? So in short: - Package 1: Contains DLLs and Runtime environment only, no binaries - Package 2: Is a launcher requiring Package 1 to function. Has binaries - Package 3: Is an editor requiring Package 1 to function. Has binaries1.3KViews0likes2CommentsHow to properly create a Framework SDK MSIX package
I'm in the process of creating MSIX distributable packages for our software project. I need to split it into multiple packages since it composes of a framework, the application using the framework and the framework SDK for others to use later on. I've created the framework package and the application package depending on it. This seems to work properly. My problem now is how to I properly create a framework SDK package? If I put all the header files and libraries under VFS/ProgramFilesX64/... then the files are hidden under WindowsApps and are only visible to packages depending on it. So my question is mostly about how I need to layout the package content to have a framework SDK which is usable.1.3KViews0likes1Comment
Recent Blog Articles
No content to show