Forum Discussion
farmerphd
Nov 13, 2023Copper Contributor
MSIX installed application on Windows 10 cannot access host machine graphics
Hello All, I am developing a Microsoft Application that is installed with a MSIX installer. The structure of the application is a *.exe application that is identified as the primary application (...
farmerphd
Nov 21, 2023Copper Contributor
Eyad-thank you for your suggestions. I explored most of these options except ensuring the manifest has the required declarations. MSIX is a great, containerized solution so will keep working to have the fully functioning MSIX package. The best solution may be for me to separate the runtime needed from the myapp.exe and have the dependency install runtime. My goal is simplicity so trying all I can before resorting to separate MSIXs.
Thanks again for your response.
farmerphd
Dec 06, 2023Copper Contributor
I finally looked at the procmon and psf support logs. I thought my problem was with opengl but it is DIrectX access. Is there an example how to include DIrectX inside the MSIX? I downloaded Microsoft.DirectXRuntime_x64 and it is a lot of dll files. Not sure how to include these inside my MSIX.
- Dec 07, 2023I believe that you can add a package dependency on DirectX to ensure that the latest version is available to your package.
But to be quite honest, I'm not sure that DirectX has changed in incompatible ways in a long time. You might need more debugging of your issue to find the real cause.- farmerphdDec 07, 2023Copper ContributorSure I need more debugging - the observation is when I split the runtime component from the .EXE app into separate packages, all works fine. It is only when I keep both in the same MSIX that the issue happend with 'opengl not installed'. The error logs show DirectX so confused on what is really happening. The clue that separate they work and together they don't is taking me down a path of understanding in package vs across package behavior. Any help is appreciated...