Forum Discussion
MSIX application is not opening ReportViewer Microsoft.ReportViewer.WinForms
I've resolved it with this:
Process.Start(Path.Combine(Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location), "PsfLauncher32.exe"));The problem was in the root path when starting it from windows start, root path for Process.Start is not the application folder when started as a store package. 🙂
I am not missing anything, I've dumped everything you've got into the folder.
Sysinternals DebugView did not catch anything but in Event Viewer there is a record of an error.
I've also tried running it in safe mode.
"Faulting application name: PsfLauncher32.exe, version: 0.0.0.0, time stamp: 0x5e66e34c
Faulting module name: PsfRuntime32.dll, version: 0.0.0.0, time stamp: 0x5e66e338
Exception code: 0xc0000409
Fault offset: 0x00028bd1
Faulting process id: 0x5dc8
Faulting application start time: 0x01d5fa3f846ea6ca
Faulting application path: C:\Programming\SyriliumRiF\Main\SyriliumRiF.MSIX\bin\x86\Release\PsfLauncher32.exe
Faulting module path: C:\Programming\SyriliumRiF\Main\SyriliumRiF.MSIX\bin\x86\Release\PsfRuntime32.dll
Report Id: 1f39b072-5917-486f-abc1-21712ebdc372"
Does anyone know something about this error regarding PsfLauncher32.exe? I did not find any useful info.
hbatrnek You may need to use a debugger to figure out what you are doing wrong. If you look in the WaitforDebugger code you'll find the lines to cause the wait. Add that into the attach code of PsfRuntime and then you can launch your app and then get your debugger to attach the process and walk through the issues.
What debugger, where? I am not a c++ dev. All I am doing is starting the exe file, it does not get simpler than that. I am double-clicking PsfLauncher32.exe with my left mouse button. 😉 I've downloaded Microsoft.PackageSupportFramework.1.0.200309.6. The problem can't be in my solution or project because it's not being used, I've stripped it to bare bones. PsfLauncher32.exe should just start the exe file next to it, and it's not doing that. How do I debug PsfLauncher32.exe that starts and immediately ends?
hbatrnek Sorry, I was assuming you were a dev. If you are not a dev you might want to build your package using a packaging tool instead of a developer build tool.
You might want to consider packaging by using the Microsoft MSIX Packaging Tool and PsfTooling. Both are free apps in the Microsoft Store. You use the Packaging Tool to capture your existing installer (or just copy files yourself). While you are still in monitoring mode after installing your app, you then run PsfTooling to inject the PSF for you. Alternatively, there are other third party packaging tools from Microsoft Partners that could be used.
