Windows Presentation Foundation
A part of the .NET Framework that provides a unified programming model for building line-of-business desktop applications on Windows.
2,783 questions
Are there alternatives to MSIX packages for .NETCore 3.1 Desktop WPF Apps hosting EFCore
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 43%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Michael
81
Reputation points
I have created a .NET Core 3.1 desktop WPF app that hosts EntityFrameworkCore. The application runs in debug mode without error.
My application requires the following Nuget packages: microsoft.entityframeworkcore, micorsoft.entityframeworkcore.sqlserver and microsoft.entityframeworkcore.tools. However, I have found that creating an MSIX package of this project will result in an application that installs but then will not open. Further, I have found that if I leave out the microsoft.entityframeworkcore.tools package, the MSIX will create an app that installs and runs until the user tries a function that leverages the EFCore methods (interesting that I can leave out this package and the app runs fine in the debugger).
While I figure out the problem with the MSIX package technique of distribution I am looking for alternative ways to deploy my application. I seems that I can't make and .msi anymore and I don't see ClickOnce for this type of build. What other options are available and practical?
M
{count} votes
-
DaisyTian-1203 11,626 Reputation points2020-08-03T06:50:59.73+00:00 How did you pack your MSIX packages with MSIX Packaging Tool or Set up your desktop application for MSIX packaging in Visual Studio? I need it to reproduce your error. What are you deploying your app for? Does Microsoft Visual Studio Installer Projects meet your needs?
-
Michael 81 Reputation points
2020-08-03T15:43:59.37+00:00 Part 1
Open VS and create a new project based on "WPF App (.NET Core) and click Create.
Open the NuGet and add microsoft.entityframeworkcore, microsoft.entityframeworkcore.sqlserver, microsoft.entityframeworkcore.tools.
Open Configuration Manager and look in the Project contexts window, click the "Platform" dropdown and select "New". For New platform select x64. Click OK. Make sure x64 is selected for the Platform (not Any CPU)
Compile and run (or Debug) to confirm the app opens. -
Michael 81 Reputation points
2020-08-03T15:44:20.59+00:00 Part 2
Add a new project for the solution, this time "Windows Application Packaging Project". Click "Create" then accept the default Win10 platforms.
Right click "Applications" and add the WPF project created in the prior steps.
Right click on the WAP project and select Publish, then Create App Packages.
Select Sideloading and uncheck "Enable automatic updates".
For demo purposes, select the "Yes, select a certificate" radiobutton and "Create". Then click Next
Change the architecture to x64 and the Solution Configuration to Debug(x64). Click Create. -
Michael 81 Reputation points
2020-08-03T15:44:44.893+00:00 Part 3
Go the the "Output Location" on the final dialog box and open the folder containing the new package. You can close this dialog box.
Open the folder containing the package. Install the certificate (the .cer file) in the Trusted Root Certification Autorities of the LOCAL MACHINE
Finally, double click on the .msixbundle file (the install package). Make sure the "Launch when ready is checked". Click Install.It should install successfully but never open (remember, it opened when you tested the app in the debugger in the beginning of this repro).
-
Michael 81 Reputation points
2020-08-03T15:45:08.88+00:00 Part 4
So, I have a WPF app with .NETCore 3.1 and EntitityFrameWorkCore. However, I can't package and distribute it because it wont run after install (check the Task Manager). Of note, there are no other ways to distribute a .NETCore with EntityFrameWorkCore because you can't use either ClickOnce nor create an .msi.
There's even more I can tell you but let's see if you can confirm the Repro. One additional item is that if you leave out microsoft.entityframeworkcore.tools and recreate the package, the app will install and run from the package until you try to use any of the the entityframeworkcore functionality programmed into the app, at that point it crashes (which you cant demo with this repro because you didn't actually use any of the EF functions).
Michael
Sign in to comment
Sign in to answer