@Amit Kumar There are a lot of things that might go wrong, and you may need to try multiple approaches.
The simplest is a Process Monitor trace. You'll easily be able to see if
- the app launches at all
- issues with finding dlls
- issues with the app not seeing files in the VFS\AppData or VFS\LocalAppData folder.
Procmon can be intimidating if you are not used to it, it is monitoring not just your app but everything unless you learn to filter things out. So for MSIX we have the PSF using the PsfTraceFixup shim.
If you package using the Psf inside, you launch a PsfLaunch exectable along with a config.json file to have it run your exectable and inject the TraceFixup into the process. This fixup doesn't modify the app behavior but will trace out the most important file and registry calls. You can an option to have it output to the debug console (which you read via a tool like SysInternals DbgView), or to a private event log (which you read with a GUI tool called PsfMonitor that is part of the Psf).
I prefer to trace with PsfTrace as it is recording the actual request by the application (intercepting at the Windows API layer) before other forms of intercepts, such as the Psf Runtime, get involved.
The command line approach is a Powershell command and requires (at least currently) that you enable Developer Mode on the PC. While I loved that approach under App-V debugging, I find I really need the tracing to figure out what is wrong unless the issue is really simple. Advanced Installer Hover is a convenient way to do this rather than the PowerShell, but it also needs Developer Mode to work.
I'll note for completeness, I always use MSIX Commander to get me an explorer in the package folder so that I can easily see the structure. This isn't an explorer running inside the container, but I can see the files and look inside them as long as I don't want to change them.
