Installing dll and header files with MSIX

%3CLINGO-SUB%20id%3D%22lingo-sub-1584369%22%20slang%3D%22en-US%22%3EInstalling%20dll%20and%20header%20files%20with%20MSIX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1584369%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20currently%20looking%20at%20redesigning%20the%20deployment%20strategy%20for%20a%20Windows%20applications%20which%20consists%20of%20a%20GUI%20application%2C%20a%20CLI%2C%20and%20a%20set%20of%20libraries.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20get%20the%20GUI%20and%20CLI%20to%20work%20as%20expected%20when%20installed%20via%20an%20MSIX%20package%2C%20but%20I'm%20having%20difficulties%20with%20the%20libraries.%20I%20want%20the%20user%20to%20access%20and%20copy%20these%20libraries%20for%20use%20in%20their%20own%20projects%2C%20but%20obviously%20when%20the%20application%20files%20are%20installed%20they're%20sandboxed%20in%20WindowsApps%2C%20so%20aren't%20meant%20to%20be%20accessible.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20deal%20with%20this%20issue%20within%20the%20MSIX%20ecosystem%3F%20Or%20do%20I%20need%20to%20deploy%20these%20libraries%20through%20some%20other%20means%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20seen%20it's%20possible%20to%20copy%20files%20outside%20of%20the%20WindowsApps%20directory%20using%20the%20Package%20Support%20Framework%20and%20Powershell%20scripts%2C%20but%20this%20doesn't%20seem%20very%20viable%20as%20the%20user%20would%20have%20to%20start%20the%20application%20before%20the%20library%20files%20would%20be%20copied.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1777780%22%20slang%3D%22en-US%22%3ERe%3A%20Installing%20dll%20and%20header%20files%20with%20MSIX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1777780%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F757203%22%20target%3D%22_blank%22%3E%40TomLewis%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20not%20sure%20I%20understand%20the%20scenario%20you%20are%20working%20within%20with%20your%20app.%20Are%20you%20able%20to%20elaborate%20more%20on%20this%3F%20What%20is%20the%20purpose%20of%20your%20app%2C%20and%20why%20would%20someone%20want%20to%20manually%20retrieve%20content%20from%20it%3F%3CBR%20%2F%3E%3CBR%20%2F%3EHave%20you%20looked%20at%20using%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fappx%2Finvoke-commandindesktoppackage%3Fview%3Dwin10-ps%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EInvoke-CommandInDesktopPackage%3C%2FA%3E%20PowerShell%20cmdlet%3F%20This%20could%20be%20used%20to%20copy%20contents%20from%20the%20apps%20VFS%20through%20PowerShell%20without%20physically%20launching%20the%20app.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1777861%22%20slang%3D%22en-US%22%3ERe%3A%20Installing%20dll%20and%20header%20files%20with%20MSIX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1777861%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F757203%22%20target%3D%22_blank%22%3E%40TomLewis%3C%2FA%3E%26nbsp%3BThe%20installation%20is%20unable%20to%20copy%20files%20outside%20of%20the%20package%20area%20by%20design%2C%20so%20you'll%20need%20something%20to%20perform%20the%20file%20copy.%26nbsp%3B%20You%20sound%20like%20you%20have%20already%20looked%20at%20using%20the%20Psf%2C%26nbsp%3B%20which%20could%20handle%20the%20task%2C%20but%20code%20in%20the%20GUI%20or%20CLI%20could%20also%20perform%20a%20copy%20as%20long%20as%20the%20destination%20is%20outside%20of%20the%20package%20boundary%2C%20much%20as%20one%20would%20write%20files%20to%20the%20user's%20Documents%20folder.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETim%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Visitor

Hi everyone,

 

I'm currently looking at redesigning the deployment strategy for a Windows applications which consists of a GUI application, a CLI, and a set of libraries.

 

I can get the GUI and CLI to work as expected when installed via an MSIX package, but I'm having difficulties with the libraries. I want the user to access and copy these libraries for use in their own projects, but obviously when the application files are installed they're sandboxed in WindowsApps, so aren't meant to be accessible.

 

Is there a way to deal with this issue within the MSIX ecosystem? Or do I need to deploy these libraries through some other means?

 

I've seen it's possible to copy files outside of the WindowsApps directory using the Package Support Framework and Powershell scripts, but this doesn't seem very viable as the user would have to start the application before the library files would be copied.

 

Thanks

2 Replies

Hi @TomLewis,

 

I'm not sure I understand the scenario you are working within with your app. Are you able to elaborate more on this? What is the purpose of your app, and why would someone want to manually retrieve content from it?

Have you looked at using the Invoke-CommandInDesktopPackage PowerShell cmdlet? This could be used to copy contents from the apps VFS through PowerShell without physically launching the app.

@TomLewis The installation is unable to copy files outside of the package area by design, so you'll need something to perform the file copy.  You sound like you have already looked at using the Psf,  which could handle the task, but code in the GUI or CLI could also perform a copy as long as the destination is outside of the package boundary, much as one would write files to the user's Documents folder.

 

Tim