SOLVED

MSIX application is not opening ReportViewer Microsoft.ReportViewer.WinForms

%3CLINGO-SUB%20id%3D%22lingo-sub-1226645%22%20slang%3D%22en-US%22%3EMSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1226645%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWhen%20I%20run%20the%20application%20exe%20file%20directly%20from%20C%3A%5CProgram%20Files%5CWindowsApps%20it%20works%2C%20but%20not%20when%20I%20start%20it%20from%20the%20Start%20menu.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EProcess%20Monito%20is%20showing%20C%3A%5CWINDOWS%5CMicrosoft.Net%5Cassembly%5CGAC_32%5CMicrosoft.ReportViewer.WinForms%5Cv4.0_14.0.0.0__89845dcd8080cc91%5CMicrosoft.ReportViewer.WinForms.dll%20PATH%20NOT%20FOUND.%20NuGet%20package%20is%20Microsoft.ReportingServices.ReportViewerControl.Winforms.%20Why%20is%20he%20looking%20there%20when%20files%20are%20in%20an%20app%20directory%3F%20I%20am%20using%20.NET%20Framework%204.8%20WPF%20and%20WindowsFormsHost%20for%20displaying%20the%20ReportViewer.%20From%20an%20explanation%20of%20how%20Package%20Support%20Framework%20works%2C%20I%20still%20don't%20know%20what%20exact%20steps%20should%20I%20take%20or%20if%20what%20process%20monitor%20shows%20is%20the%20root%20problem.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1226744%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1226744%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20this%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpsf%2Fpackage-support-framework%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpsf%2Fpackage-support-framework%3C%2FA%3E%2C%26nbsp%3Bapplication%20runs%20but%20the%20issue%20stays%2C%20it%20will%20not%20open%20window%20with%20the%20report%20viewer%20on%20it%20and%20it%20does%20not%20throw%20an%20exception.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20the%20issue%20is%20in%20config.json%2C%20I%20am%20not%20sure%20how%20to%20configure%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPackage.appxmanifest%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%0A%0A%3CPACKAGE%20xmlns%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%22%20uap%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Fuap%2Fwindows10%22%20rescap%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%22%20ignorablenamespaces%3D%22uap%20rescap%22%3E%0A%0A%20%20%3CIDENTITY%20name%3D%22a1ddc6e0-bb40-49b3-8e57-6a0646b7f49d%22%20publisher%3D%22CN%3DTRUE%20IT%2C%20O%3DTRUE%20IT%2C%20C%3DHR%22%20version%3D%221.0.72.0%22%3E%3C%2FIDENTITY%3E%0A%0A%20%20%3CPROPERTIES%3E%0A%20%20%20%20%3CDISPLAYNAME%3ESyriliumRiF%3C%2FDISPLAYNAME%3E%0A%20%20%20%20%3CPUBLISHERDISPLAYNAME%3ETRUE%20IT%3C%2FPUBLISHERDISPLAYNAME%3E%0A%20%20%20%20%3CLOGO%3EImages%5CStoreLogo.png%3C%2FLOGO%3E%0A%20%20%3C%2FPROPERTIES%3E%0A%0A%20%20%3CDEPENDENCIES%3E%0A%20%20%20%20%3CTARGETDEVICEFAMILY%20name%3D%22Windows.Universal%22%20minversion%3D%2210.0.0.0%22%20maxversiontested%3D%2210.0.0.0%22%3E%3C%2FTARGETDEVICEFAMILY%3E%0A%20%20%20%20%3CTARGETDEVICEFAMILY%20name%3D%22Windows.Desktop%22%20minversion%3D%2210.0.14393.0%22%20maxversiontested%3D%2210.0.14393.0%22%3E%3C%2FTARGETDEVICEFAMILY%3E%0A%20%20%3C%2FDEPENDENCIES%3E%0A%0A%20%20%3CRESOURCES%3E%0A%20%20%20%20%3CRESOURCE%20language%3D%22x-generate%22%3E%3C%2FRESOURCE%3E%0A%20%20%3C%2FRESOURCES%3E%0A%0A%20%20%3CAPPLICATIONS%3E%0A%20%20%20%20%20%20%20%3CAPPLICATION%20id%3D%22App%22%20executable%3D%22PSFLauncher32.exe%22%20entrypoint%3D%22Windows.FullTrustApplication%22%3E%0A%20%20%20%20%20%20%20%3CVISUALELEMENTS%20displayname%3D%22SyriliumRiF%22%20description%3D%22SyriliumRiF%22%20square150x150logo%3D%22Images%5CSquare150x150Logo.png%22%20square44x44logo%3D%22Images%5CSquare44x44Logo.png%22%20backgroundcolor%3D%22white%22%3E%0A%20%20%20%20%20%20%20%20%3CDEFAULTTILE%20wide310x150logo%3D%22Images%5CWide310x150Logo.png%22%20square71x71logo%3D%22Images%5CSmallTile.png%22%20square310x310logo%3D%22Images%5CLargeTile.png%22%3E%0A%20%20%20%20%20%20%20%20%3C%2FDEFAULTTILE%3E%0A%20%20%20%20%20%20%20%20%3CSPLASHSCREEN%20image%3D%22Images%5CSplashScreen.png%22%3E%3C%2FSPLASHSCREEN%3E%0A%20%20%20%20%20%20%20%20%3CLOCKSCREEN%20badgelogo%3D%22Images%5CBadgeLogo.png%22%20notification%3D%22badgeAndTileText%22%3E%3C%2FLOCKSCREEN%3E%0A%20%20%20%20%20%20%3C%2FVISUALELEMENTS%3E%20%0A%20%20%20%20%3C%2FAPPLICATION%3E%0A%20%20%3C%2FAPPLICATIONS%3E%0A%0A%20%20%3CCAPABILITIES%3E%0A%20%20%20%20%3CCAPABILITY%20name%3D%22internetClient%22%3E%3C%2FCAPABILITY%3E%0A%20%20%20%20%3CCAPABILITY%20name%3D%22runFullTrust%22%3E%3C%2FCAPABILITY%3E%0A%20%20%3C%2FCAPABILITIES%3E%0A%3C%2FPACKAGE%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Econfig.json%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-javascript%22%3E%3CCODE%3E%7B%0A%20%20%22applications%22%3A%20%5B%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%22id%22%3A%20%22App%22%2C%0A%20%20%20%20%20%20%22executable%22%3A%20%22SyriliumRiF.exe%22%2C%0A%20%20%20%20%20%20%22workingDirectory%22%3A%20%22%2F%22%0A%20%20%20%20%7D%0A%20%20%5D%2C%0A%20%20%22processes%22%3A%20%5B%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%22executable%22%3A%20%22SyriliumRiF%22%2C%0A%20%20%20%20%20%20%22fixups%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%22dll%22%3A%20%22FileRedirectionFixup32.dll%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22config%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22redirectedPaths%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22packageRelative%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22base%22%3A%20%22%2F%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22patterns%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22.*%5C%5C.dll%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%5D%0A%20%20%20%20%7D%0A%20%20%5D%0A%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1227114%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1227114%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%20For%20a%20dll%20not%20found%20issue%2C%20assuming%20the%20dll%20is%20in%20your%20package%20you%20should%20probably%20try%20adding%20DynamicLibraryFixup.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20fixup%20was%20developed%20to%20ensure%20the%20exe%20will%20find%20any%20dll%20inside%20the%20package%2C%20overcoming%20issues%20due%20to%20working%20directory%2C%20path%20variables%20not%20being%20supported%2C%20and%20AppPaths%20not%20being%20supported.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20may%20be%20included%20in%20addition%20to%20the%20FileRedirectionFixup.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1227964%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1227964%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20sideloading%20my%20package%2C%20not%20through%20the%20store%20and%20I%20have%20an%20MSIX%20project%20with%20Package.appxmanifest%20file.%20The%20problem%20is%20no%20matter%20what%20I%20enter%20in%20this%20part%20(you%20can%20see%20the%26nbsp%3Bzulzu.exe%20file%20which%20does%20not%20exist)%3A%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%20%3CAPPLICATIONS%3E%0A%20%20%20%20%3CAPPLICATION%20id%3D%22App%22%20executable%3D%22zulzu.exe%22%20entrypoint%3D%22%24targetentrypoint%24%22%3E%0A%20%20%20%20%20%20%3CVISUALELEMENTS%20displayname%3D%22SyriliumRiF%22%20description%3D%22SyriliumRiF%22%20square150x150logo%3D%22Images%5CSquare150x150Logo.png%22%20square44x44logo%3D%22Images%5CSquare44x44Logo.png%22%20backgroundcolor%3D%22white%22%3E%0A%20%20%20%20%20%20%20%20%3CDEFAULTTILE%20wide310x150logo%3D%22Images%5CWide310x150Logo.png%22%20square71x71logo%3D%22Images%5CSmallTile.png%22%20square310x310logo%3D%22Images%5CLargeTile.png%22%3E%0A%20%20%20%20%20%20%20%20%3C%2FDEFAULTTILE%3E%0A%20%20%20%20%20%20%20%20%3CSPLASHSCREEN%20image%3D%22Images%5CSplashScreen.png%22%3E%3C%2FSPLASHSCREEN%3E%0A%20%20%20%20%20%20%20%20%3CLOCKSCREEN%20badgelogo%3D%22Images%5CBadgeLogo.png%22%20notification%3D%22badgeAndTileText%22%3E%3C%2FLOCKSCREEN%3E%0A%20%20%20%20%20%20%3C%2FVISUALELEMENTS%3E%0A%20%20%20%20%3C%2FAPPLICATION%3E%0A%20%20%3C%2FAPPLICATIONS%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3Bthe%20real%20exe%20starts%20normally%2C%20that%20is%20saying%20that%26nbsp%3B%3CSPAN%3EPSFLauncher32.exe%20was%20never%20started%20when%20in%20Executable%2C%20but%20if%20I%20am%20to%20delete%20this%20whole%20Applications%20section%20the%20package%20complains%20so%2C%20this%20manifest%20file%20is%20being%20used%20but%20that%20Application%20part%20is%20ignored%2C%20why%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228132%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228132%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%20It%20should%20be%20like%20this%20for%20MSIX%3A%3C%2FP%3E%0A%3CP%3EEntryPoint%3D%22Windows.FullTrustApplication%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228313%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228313%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149589%22%20target%3D%22_blank%22%3E%40Tim%20Mangan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20that%20and%20when%20I%20go%20to%20Publish%20%26gt%3B%20Create%20App%20Package%20on%20the%20Windows%20Application%20Package%20Project%2C%20he%26nbsp%3Bjust%20overrides%20whatever%20I've%20entered%20in%20Application%20%26gt%3B%20Executable%20with%20the%20executable%20from%20the%20referenced%20project.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22hbatrnek_0-1584181880820.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F176929i936676FBAF5B4F6B%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22hbatrnek_0-1584181880820.png%22%20alt%3D%22hbatrnek_0-1584181880820.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EPackage.appxmanifest%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%20%3CAPPLICATIONS%3E%0A%20%20%20%20%3CAPPLICATION%20id%3D%22App%22%20executable%3D%22PsfLauncher32.exe%22%20entrypoint%3D%22Windows.FullTrustApplication%22%3E%0A%20%20%20%20%20%20%3CVISUALELEMENTS%20displayname%3D%22SyriliumRiF%22%20description%3D%22SyriliumRiF%22%20square150x150logo%3D%22Images%5CSquare150x150Logo.png%22%20square44x44logo%3D%22Images%5CSquare44x44Logo.png%22%20backgroundcolor%3D%22white%22%3E%0A%20%20%20%20%20%20%20%20%3CDEFAULTTILE%20wide310x150logo%3D%22Images%5CWide310x150Logo.png%22%20square71x71logo%3D%22Images%5CSmallTile.png%22%20square310x310logo%3D%22Images%5CLargeTile.png%22%3E%0A%20%20%20%20%20%20%20%20%3C%2FDEFAULTTILE%3E%0A%20%20%20%20%20%20%20%20%3CSPLASHSCREEN%20image%3D%22Images%5CSplashScreen.png%22%3E%3C%2FSPLASHSCREEN%3E%0A%20%20%20%20%20%20%20%20%3CLOCKSCREEN%20badgelogo%3D%22Images%5CBadgeLogo.png%22%20notification%3D%22badgeAndTileText%22%3E%3C%2FLOCKSCREEN%3E%0A%20%20%20%20%20%20%3C%2FVISUALELEMENTS%3E%0A%20%20%20%20%3C%2FAPPLICATION%3E%0A%20%20%3C%2FAPPLICATIONS%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESyriliumRiF.MSIX_1.0.80.0_x86.appx%20oppened%20with%20MSIX%20Packaging%20Tool%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%20%20%3CAPPLICATIONS%3E%0A%20%20%20%20%3CAPPLICATION%20id%3D%22App%22%20executable%3D%22SyriliumRiF.exe%22%20entrypoint%3D%22Windows.FullTrustApplication%22%3E%0A%20%20%20%20%20%20%3CVISUALELEMENTS%20displayname%3D%22SyriliumRiF%22%20description%3D%22SyriliumRiF%22%20square150x150logo%3D%22Images%5CSquare150x150Logo.png%22%20square44x44logo%3D%22Images%5CSquare44x44Logo.png%22%20backgroundcolor%3D%22white%22%3E%0A%20%20%20%20%20%20%20%20%3CDEFAULTTILE%20wide310x150logo%3D%22Images%5CWide310x150Logo.png%22%20square71x71logo%3D%22Images%5CSmallTile.png%22%20square310x310logo%3D%22Images%5CLargeTile.png%22%3E%3C%2FDEFAULTTILE%3E%0A%20%20%20%20%20%20%20%20%3CSPLASHSCREEN%20image%3D%22Images%5CSplashScreen.png%22%3E%3C%2FSPLASHSCREEN%3E%0A%20%20%20%20%20%20%20%20%3CLOCKSCREEN%20badgelogo%3D%22Images%5CBadgeLogo.png%22%20notification%3D%22badgeAndTileText%22%3E%3C%2FLOCKSCREEN%3E%0A%20%20%20%20%20%20%3C%2FVISUALELEMENTS%3E%0A%20%20%20%20%3C%2FAPPLICATION%3E%0A%20%20%3C%2FAPPLICATIONS%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20know%20how%20to%20stop%20him%20from%20overriding%20what%20I've%20entered.%3C%2FP%3E%3CP%3EThe%20solution%20that%20comes%20to%20mind%20is%20creating%20another%20executable%20project%20that%20I%20can%20reference%20and%20that%20starts%20the%26nbsp%3B%3CSTRONG%3EPsfLauncher32.exe%2C%20I'll%20try%20that.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228398%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228398%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%20I%20don't%20build%20packages%20that%20way%2C%20so%20not%20sure%20I%20can%20help%20much.%26nbsp%3B%20But%20bringing%20in%20PsfLauncher%20does%20require%20an%20extra%20field%20not%20present%20(ID)%20in%20your%20examples%20that%20PsfLauncher%20(not%20the%20building%20tools)%20requires.%26nbsp%3B%20I'll%20show%20a%20working%20example%20below%2C%20but%20the%20value%20of%20ID%20is%20a%20munging%20of%20the%20name%20of%20the%20executable%20in%20uppercase%2C%20with%20exe%20dropped%2C%20and%20number%20characters%20converted%20to%20equivalent%20English%20string.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBut%20here%20is%20a%20properly%20formed%20manifest%20that%20was%20created%20using%20the%20MSIX%20Packaging%20Tool%20(which%20I%20know%20isn't%20how%20you%20want%20to%20build%20your%20package).%20The%20example%20uses%20the%2064%20bit%20version%20of%20PsfLauncher.%26nbsp%3B%20File%20paths%20in%20this%20example%20are%20different%20because%20I%20didn't%20put%20them%20at%20the%20root%20folder%20of%20the%20package%2C%20so%20you%20would%20not%20have%20the%20%22VFS%5C%E2%80%A6%22%20file%20path%20in%20your%20references.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3C!--Package%20created%20by%20MSIX%20Packaging%20Tool%20version%3A%201.2019.1220.0--%3E%0A%3CIDENTITY%20processorarchitecture%3D%22x64%22%20version%3D%223.26.2.0%22%20publisher%3D%22CN%3DTMurgent.local%22%20name%3D%22FileZilla-Scripts10%22%3E%3C%2FIDENTITY%3E%0A%3CPROPERTIES%3E%0A%20%20%20%20%3CDISPLAYNAME%3EFileZilla%3C%2FDISPLAYNAME%3E%0A%20%20%20%20%3CPUBLISHERDISPLAYNAME%3EFileZilla%20(Packaged%20by%20TMurgent)%3C%2FPUBLISHERDISPLAYNAME%3E%0A%20%20%20%20%3CDESCRIPTION%3ENone%3C%2FDESCRIPTION%3E%0A%20%20%20%20%3CLOGO%3EAssets%5CStoreLogo.png%3C%2FLOGO%3E%0A%3C%2FPROPERTIES%3E%0A%0A%3CRESOURCES%3E%0A%20%20%20%20%3CRESOURCE%20language%3D%22en-us%22%3E%3C%2FRESOURCE%3E%0A%3C%2FRESOURCES%3E%0A%0A%3CDEPENDENCIES%3E%0A%20%20%20%20%3CTARGETDEVICEFAMILY%20name%3D%22Windows.Desktop%22%20maxversiontested%3D%2210.0.18335.0%22%20minversion%3D%2210.0.17763.0%22%3E%3C%2FTARGETDEVICEFAMILY%3E%0A%3C%2FDEPENDENCIES%3E%0A%0A%3CCAPABILITIES%3E%0A%20%20%20%20%3CCAPABILITY%20name%3D%22runFullTrust%22%3E%3C%2FCAPABILITY%3E%0A%3C%2FCAPABILITIES%3E%0A%0A%3CAPPLICATIONS%3E%0A%20%20%20%20%3CAPPLICATION%20entrypoint%3D%22Windows.FullTrustApplication%22%20executable%3D%22VFS%5CProgramFilesX64%5CFileZilla%20FTP%20Client%5CPsfLauncher1.exe%22%20id%3D%22PSFLAUNCHEROne%22%3E%0A%0A%20%20%20%20%20%20%20%20%3CVISUALELEMENTS%20description%3D%22FileZilla%22%20square44x44logo%3D%22Assets%5CSquare44x44Logo.png%22%20square150x150logo%3D%22Assets%5CSquare150x150Logo.png%22%20displayname%3D%22FileZilla%22%20backgroundcolor%3D%22transparent%22%3E%0A%20%20%20%20%20%20%20%20%20%20%20%20%3CDEFAULTTILE%20square71x71logo%3D%22Assets%5CSquare71x71Logo.png%22%20square310x310logo%3D%22Assets%5CSquare310x310Logo.png%22%20wide310x150logo%3D%22Assets%5CWide310x150Logo.png%22%3E%3C%2FDEFAULTTILE%3E%0A%20%20%20%20%20%20%20%20%3C%2FVISUALELEMENTS%3E%0A%20%20%20%20%3C%2FAPPLICATION%3E%0A%3C%2FAPPLICATIONS%3E%0A%0A%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3C!--Package%20created%20by%20MSIX%20Packaging%20Tool%20version%3A%201.2019.1220.0--%3E%0A%0A%3CP%3EPerhaps%20this%20can%20help%20you%20sort%20things%20out.%26nbsp%3B%20I'm%20unfamiliar%20with%20the%20FWK%20file%20reference%20in%20your%20project%20example%2C%20but%20possibly%20your%20issue%20starts%20there.%26nbsp%3B%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228664%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228664%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20my%20exe%20project%20that%20starts%20PsfLauncher32%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-csharp%22%3E%3CCODE%3E%20%20%20%20class%20Program%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20static%20void%20Main(string%5B%5D%20args)%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20Process.Start(%22PsfLauncher32.exe%22)%3B%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3Band%20this%20is%20the%20config.json%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-javascript%22%3E%3CCODE%3E%7B%0A%20%20%22applications%22%3A%20%5B%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%22id%22%3A%20%22App%22%2C%0A%20%20%20%20%20%20%22executable%22%3A%20%22SyriliumRiF.exe%22%2C%0A%20%20%20%20%20%20%22workingDirectory%22%3A%20%22%2F%22%0A%20%20%20%20%7D%0A%20%20%5D%2C%0A%20%20%22processes%22%3A%20%5B%0A%20%20%20%20%7B%0A%20%20%20%20%20%20%22executable%22%3A%20%22SyriliumRiF%22%2C%0A%20%20%20%20%20%20%22fixups%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%22dll%22%3A%20%22FileRedirectionFixup32.dll%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22config%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22redirectedPaths%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22packageRelative%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22base%22%3A%20%22%2F%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22patterns%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22*%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%22dll%22%3A%20%22TraceFixup32.dll%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22config%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22traceLevels%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22filesystem%22%3A%20%22allFailures%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%22dll%22%3A%20%22DynamicLibraryFixup32.dll%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22config%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22traceLevels%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22filesystem%22%3A%20%22allFailures%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%5D%0A%20%20%20%20%7D%0A%20%20%5D%0A%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20is%26nbsp%3BPsfLauncher32%20not%20starting%26nbsp%3BSyriliumRiF.exe%3F%3C%2FP%3E%3CP%3EWho%20is%20reading%20the%20config.json%2C%20is%20PsfLauncher32%20reading%20it%3F%3C%2FP%3E%3CP%3EWhat%20parameters%20do%20I%20need%20to%20send%20to%26nbsp%3BPsfLauncher32.exe%2C%20what%20would%20be%20the%20command%20line%20call%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228722%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228722%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EWho%20is%20reading%20the%20config.json%2C%20is%20PsfLauncher32%20reading%20it%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%26nbsp%3B%20In%20the%20PsfLauncherXX.exe%20process%2C%26nbsp%3B%20PsfRuntimeXX.dll%20will%20initially%20read%20the%20config.json%20file%20for%20the%20%22applications%22%20section%20at%20the%20top%20of%20the%20file.%26nbsp%3B%20It%20is%20this%20runtime%20that%20will%20process%20the%20instructions%20for%20the%20matching%20application%20ID%20(based%20on%20process%20name%20munging%20mentioned%20previously).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20the%20PsfRuntime%20launches%20your%20target%20process%2C%20it%20injects%20another%20copy%20of%20PsfRuntime%20into%20that%20process.%26nbsp%3B%20This%20secondary%20copy%20will%20re-read%20the%20config.json%20file%20for%20the%20purpose%20of%20handling%20the%20bottom%20half%20(%22processes%22)%20to%20determine%20which%20other%20dlls%20to%20inject%20and%20provide%20those%20injected%20dlls%20with%20their%20configuration.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228720%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228720%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F506378%22%20target%3D%22_blank%22%3E%40hbatrnek%3C%2FA%3E%20Perhaps%20you%20are%20missing%20PsfRuntime32.dll%3F%26nbsp%3B%20I%20see%20you%20have%20the%20exe%20but%20we%20always%20use%20the%20dll.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%3A%20PsfLauncher%2C%20even%20the%20release%20build%2C%20will%20always%20output%20to%20the%20debug%20port.%20So%20run%20Sysinternals%20DebugView%20on%20the%20side%20to%20see%20what%20it%20might%20be%20telling%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1228735%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20application%20is%20not%20opening%20ReportViewer%20Microsoft.ReportViewer.WinForms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1228735%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149589%22%20target%3D%22_blank%22%3E%40Tim%20Mangan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESysinternals%20DebugView%20did%20not%20catch%20anything%20but%20in%20Event%20Viewer%20there%20is%20a%20record%20of%20an%20error%3A%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

When I run the application exe file directly from C:\Program Files\WindowsApps it works, but not when I start it from the Start menu.

Process Monito is showing C:\WINDOWS\Microsoft.Net\assembly\GAC_32\Microsoft.ReportViewer.WinForms\v4.0_14.0.0.0__89845dcd8080cc91\Microsoft.ReportViewer.WinForms.dll PATH NOT FOUND. NuGet package is Microsoft.ReportingServices.ReportViewerControl.Winforms. Why is he looking there when files are in an app directory? I am using .NET Framework 4.8 WPF and WindowsFormsHost for displaying the ReportViewer. From an explanation of how Package Support Framework works, I still don't know what exact steps should I take or if what process monitor shows is the root problem.

23 Replies

@hbatrnek 

I've tried this https://docs.microsoft.com/en-us/windows/msix/psf/package-support-framework, application runs but the issue stays, it will not open window with the report viewer on it and it does not throw an exception.

 

Maybe the issue is in config.json, I am not sure how to configure it.

 

Package.appxmanifest:

<?xml version="1.0" encoding="utf-8"?>

<Package
  xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10"
  xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10"
  xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
  IgnorableNamespaces="uap rescap">

  <Identity
    Name="a1ddc6e0-bb40-49b3-8e57-6a0646b7f49d"
    Publisher="CN=TRUE IT, O=TRUE IT, C=HR"
    Version="1.0.72.0" />

  <Properties>
    <DisplayName>SyriliumRiF</DisplayName>
    <PublisherDisplayName>TRUE IT</PublisherDisplayName>
    <Logo>Images\StoreLogo.png</Logo>
  </Properties>

  <Dependencies>
    <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" />
    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.14393.0" MaxVersionTested="10.0.14393.0" />
  </Dependencies>

  <Resources>
    <Resource Language="x-generate"/>
  </Resources>

  <Applications>
  	    <Application Id="App"
                 Executable="PSFLauncher32.exe"
                 EntryPoint="Windows.FullTrustApplication">
       <uap:VisualElements
        DisplayName="SyriliumRiF"
        Description="SyriliumRiF"
        Square150x150Logo="Images\Square150x150Logo.png"
        Square44x44Logo="Images\Square44x44Logo.png"   BackgroundColor="white">
        <uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png"  Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png" >
        </uap:DefaultTile >
        <uap:SplashScreen Image="Images\SplashScreen.png"  />
        <uap:LockScreen BadgeLogo="Images\BadgeLogo.png" Notification="badgeAndTileText"/>
      </uap:VisualElements> 
    </Application>
  </Applications>

  <Capabilities>
    <Capability Name="internetClient" />
    <rescap:Capability Name="runFullTrust" />
  </Capabilities>
</Package>

 

config.json:

{
  "applications": [
    {
      "id": "App",
      "executable": "SyriliumRiF.exe",
      "workingDirectory": "/"
    }
  ],
  "processes": [
    {
      "executable": "SyriliumRiF",
      "fixups": [
        {
          "dll": "FileRedirectionFixup32.dll",
          "config": {
            "redirectedPaths": {
              "packageRelative": [
                {
                  "base": "/",
                  "patterns": [
                    ".*\\.dll"
                  ]
                }
              ]
            }
          }
        }
      ]
    }
  ]
}

 

@hbatrnek For a dll not found issue, assuming the dll is in your package you should probably try adding DynamicLibraryFixup. 

 

This fixup was developed to ensure the exe will find any dll inside the package, overcoming issues due to working directory, path variables not being supported, and AppPaths not being supported.

 

It may be included in addition to the FileRedirectionFixup.

@TIMOTHY MANGAN 

I am sideloading my package, not through the store and I have an MSIX project with Package.appxmanifest file. The problem is no matter what I enter in this part (you can see the zulzu.exe file which does not exist): 

 <Applications>
    <Application Id="App"
      Executable="zulzu.exe"
      EntryPoint="$targetentrypoint$">
      <uap:VisualElements
        DisplayName="SyriliumRiF"
        Description="SyriliumRiF"
        Square150x150Logo="Images\Square150x150Logo.png"
        Square44x44Logo="Images\Square44x44Logo.png"   BackgroundColor="white">
        <uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png"  Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png" >
        </uap:DefaultTile >
        <uap:SplashScreen Image="Images\SplashScreen.png"  />
        <uap:LockScreen BadgeLogo="Images\BadgeLogo.png" Notification="badgeAndTileText"/>
      </uap:VisualElements>
    </Application>
  </Applications>

 the real exe starts normally, that is saying that PSFLauncher32.exe was never started when in Executable, but if I am to delete this whole Applications section the package complains so, this manifest file is being used but that Application part is ignored, why?

@hbatrnek It should be like this for MSIX:

EntryPoint="Windows.FullTrustApplication"

@Tim Mangan 

I've tried that and when I go to Publish > Create App Package on the Windows Application Package Project, he just overrides whatever I've entered in Application > Executable with the executable from the referenced project. 

hbatrnek_0-1584181880820.png

Package.appxmanifest:

 

 

 <Applications>
    <Application Id="App"
      Executable="PsfLauncher32.exe"
      EntryPoint="Windows.FullTrustApplication">
      <uap:VisualElements
        DisplayName="SyriliumRiF"
        Description="SyriliumRiF"
        Square150x150Logo="Images\Square150x150Logo.png"
        Square44x44Logo="Images\Square44x44Logo.png"   BackgroundColor="white">
        <uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png"  Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png" >
        </uap:DefaultTile >
        <uap:SplashScreen Image="Images\SplashScreen.png"  />
        <uap:LockScreen BadgeLogo="Images\BadgeLogo.png" Notification="badgeAndTileText"/>
      </uap:VisualElements>
    </Application>
  </Applications>

 

 

SyriliumRiF.MSIX_1.0.80.0_x86.appx oppened with MSIX Packaging Tool:

 

 

  <Applications>
    <Application Id="App" Executable="SyriliumRiF.exe" EntryPoint="Windows.FullTrustApplication">
      <uap:VisualElements DisplayName="SyriliumRiF" Description="SyriliumRiF" Square150x150Logo="Images\Square150x150Logo.png" Square44x44Logo="Images\Square44x44Logo.png" BackgroundColor="white">
        <uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png" Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png"></uap:DefaultTile>
        <uap:SplashScreen Image="Images\SplashScreen.png" />
        <uap:LockScreen BadgeLogo="Images\BadgeLogo.png" Notification="badgeAndTileText" />
      </uap:VisualElements>
    </Application>
  </Applications>

 

 

I don't know how to stop him from overriding what I've entered.

The solution that comes to mind is creating another executable project that I can reference and that starts the PsfLauncher32.exe, I'll try that.

 

@hbatrnek I don't build packages that way, so not sure I can help much.  But bringing in PsfLauncher does require an extra field not present (ID) in your examples that PsfLauncher (not the building tools) requires.  I'll show a working example below, but the value of ID is a munging of the name of the executable in uppercase, with exe dropped, and number characters converted to equivalent English string.

 

But here is a properly formed manifest that was created using the MSIX Packaging Tool (which I know isn't how you want to build your package). The example uses the 64 bit version of PsfLauncher.  File paths in this example are different because I didn't put them at the root folder of the package, so you would not have the "VFS\…" file path in your references.

 

<!--Package created by MSIX Packaging Tool version: 1.2019.1220.0-->
<Identity ProcessorArchitecture="x64" Version="3.26.2.0" Publisher="CN=TMurgent.local" Name="FileZilla-Scripts10"/>
<Properties>
    <DisplayName>FileZilla</DisplayName>
    <PublisherDisplayName>FileZilla (Packaged by TMurgent)</PublisherDisplayName>
    <Description>None</Description>
    <Logo>Assets\StoreLogo.png</Logo>
</Properties>

<Resources>
    <Resource Language="en-us"/>
</Resources>

<Dependencies>
    <TargetDeviceFamily Name="Windows.Desktop" MaxVersionTested="10.0.18335.0"   MinVersion="10.0.17763.0"/>
</Dependencies>

<Capabilities>
    <rescap:Capability Name="runFullTrust"/>
</Capabilities>

<Applications>
    <Application EntryPoint="Windows.FullTrustApplication" Executable="VFS\ProgramFilesX64\FileZilla FTP Client\PsfLauncher1.exe" Id="PSFLAUNCHEROne">

        <uap:VisualElements Description="FileZilla" Square44x44Logo="Assets\Square44x44Logo.png" Square150x150Logo="Assets\Square150x150Logo.png" DisplayName="FileZilla" BackgroundColor="transparent">
            <uap:DefaultTile Square71x71Logo="Assets\Square71x71Logo.png" Square310x310Logo="Assets\Square310x310Logo.png" Wide310x150Logo="Assets\Wide310x150Logo.png"/>
        </uap:VisualElements>
    </Application>
</Applications>

</Package><!--Package created by MSIX Packaging Tool version: 1.2019.1220.0-->

Perhaps this can help you sort things out.  I'm unfamiliar with the FWK file reference in your project example, but possibly your issue starts there. 

@TIMOTHY MANGAN 

This is my exe project that starts PsfLauncher32:

 

 

 

    class Program
    {
        static void Main(string[] args)
        {
            Process.Start("PsfLauncher32.exe");
        }
    }

 

 

 

 and this is the config.json:

 

 

 

{
  "applications": [
    {
      "id": "App",
      "executable": "SyriliumRiF.exe",
      "workingDirectory": "/"
    }
  ],
  "processes": [
    {
      "executable": "SyriliumRiF",
      "fixups": [
        {
          "dll": "FileRedirectionFixup32.dll",
          "config": {
            "redirectedPaths": {
              "packageRelative": [
                {
                  "base": "/",
                  "patterns": [
                    "*"
                  ]
                }
              ]
            }
          }
        },
        {
          "dll": "TraceFixup32.dll",
          "config": {
            "traceLevels": {
              "filesystem": "allFailures"
            }
          }
        },
        {
          "dll": "DynamicLibraryFixup32.dll",
          "config": {
            "traceLevels": {
              "filesystem": "allFailures"
            }
          }
        }
      ]
    }
  ]
}

 

 

 

Why is PsfLauncher32 not starting SyriliumRiF.exe?

Who is reading the config.json, is PsfLauncher32 reading it?

What parameters do I need to send to PsfLauncher32.exe, what would be the command line call?

 

@hbatrnek Perhaps you are missing PsfRuntime32.dll?  I see you have the exe but we always use the dll.  

 

Also: PsfLauncher, even the release build, will always output to the debug port. So run Sysinternals DebugView on the side to see what it might be telling you.

 


@hbatrnek wrote:

Who is reading the config.json, is PsfLauncher32 reading it?

 

@hbatrnek  In the PsfLauncherXX.exe process,  PsfRuntimeXX.dll will initially read the config.json file for the "applications" section at the top of the file.  It is this runtime that will process the instructions for the matching application ID (based on process name munging mentioned previously).

 

When the PsfRuntime launches your target process, it injects another copy of PsfRuntime into that process.  This secondary copy will re-read the config.json file for the purpose of handling the bottom half ("processes") to determine which other dlls to inject and provide those injected dlls with their configuration.

@Tim Mangan 

Sysinternals DebugView did not catch anything but in Event Viewer there is a record of an error:

 
 
 
 

"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
Faulting package full name:
Faulting package-relative application ID: "

@Tim Mangan 

 

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"

@hbatrnek 

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.

@Tim Mangan 

 

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.  

@Tim Mangan 

I've managed to build the CentennialFixups solution and the first problem is that ::GetCurrentPackageFamilyName(&length, nullptr)  == APPMODEL_ERROR_NO_PACKAGE

"The process has no package identity." 

What other files or setup is he expecting?

I am really not keen on learning C++ just because of this program and MSIX Packaging Tool is not an option because I have my own solution in C# .NET Framework 4.8 that I want to be packaged and distributed. ;) What are the requirements of the PsfLauncher, is he expecting the MSIX package or what? Logic would say that PsfLauncher should first read the config.json to be able to find other files or packages if necessary which he is not doing because psf::is_packaged() returns false.

 

 

 

 

 

	inline bool is_packaged() noexcept
	{
		UINT32 length = 0;
		return ::GetCurrentPackageFamilyName(&length, nullptr) != APPMODEL_ERROR_NO_PACKAGE;
	}

 

 

 

 

 

 

@hbatrnek 

If I am to force that is_packaged == true then it returns error "Unable to read memory".

hbatrnek_0-1584394724600.png

 

I presume that the program needs to be started from the windows start menu because then he is wrapped in that windows store package. I am going back to trying this in a packaged environment:

 

void attach()
{
    psf::wait_for_debugger();

 

 

@hbatrnek 

Now I realized that the packaged application default directory is c:\windows\system32 and that is why he is unable to Process.Start the exe in the project directory. "System.ComponentModel.Win32Exception: 'The system cannot find the file specified'". What am I supposed to do, is PsfLauncher unable to work with the Windows Application Packaging Project in Visual Studio? 

When you do this:

hbatrnek_0-1584397848135.png

he overrides PsfLauncher32.exe

 

 <Applications>
 	    <Application Id="SyriliumRiF"
      Executable="PsfLauncher32.exe"
      EntryPoint="Windows.FullTrustApplication">
      <uap:VisualElements
        DisplayName="SyriliumRiF"
        Description="SyriliumRiF"
        Square150x150Logo="Images\Square150x150Logo.png"
        Square44x44Logo="Images\Square44x44Logo.png"   BackgroundColor="white">
        <uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png"  Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png" >
        </uap:DefaultTile >
        <uap:SplashScreen Image="Images\SplashScreen.png"  />
        <uap:LockScreen BadgeLogo="Images\BadgeLogo.png" Notification="badgeAndTileText"/>
      </uap:VisualElements>
    </Application>
  </Applications>

 

with project's exe referenced in:

hbatrnek_1-1584397973341.png

Was anyone able to solve this or it's unsolvable for the moment?

Did anyone try to solve this through Windows Application Packaging Project?

MSIX Packaging Tool seems crap to me because he is doing packaging by the principle of recording what program is doing and accessing, that is not what I want for my VS solution, for VS solution they've created a Windows Application Packaging Project, but maybe it's still in its infancy.

@hbatrnek To set the working directory to the root of the package folder, in the manifest use 

WorkingDirectory = ""