Forum Discussion
Solved
Is It Possible To Use Publish Single File In .Net Core 3 With AppInstaller/MSIX?
Hi,
Where I work we have a WPF application that we converted to .NET Core 3.0 and migrated to MSIX/AppInstaller from ClickOnce. I noticed that .NET Core 3.0 has the ability to publish as a single file. However if I add this setting to my .csproj for my WPF application and/or make modifications to the .wapproj:
<ItemGroup>
<ProjectReference Include="..\..\Application\MyWpfDotNetCore3App.csproj">
<DesktopBridgeSelfContained>True</DesktopBridgeSelfContained>
<DesktopBridgeIdentifier>win-x64</DesktopBridgeIdentifier>
<Properties>SelfContained=%(DesktopBridgeSelfContained);RuntimeIdentifier=%(DesktopBridgeIdentifier);PublishReadyToRun=true</Properties>
<SkipGetTargetFrameworkProperties>True</SkipGetTargetFrameworkProperties>
</ProjectReference>
</ItemGroup>
And then publish or build the MSIX and AppInstaller files (either using VS or Azure Devops), the MSIX bundle still contains all of the loose files for the app and its dependencies.
This isn't really an issue, but I would just like to know if MSIX/AppInstaller currently supports this functionality or if I am doing something wrong?
This isn't really an issue, but I would just like to know if MSIX/AppInstaller currently supports this functionality or if I am doing something wrong?
When using the Windows Application Packaging Project with .NET Core 3 it creates an app-local .NET Core package which is fully self contained. The single file, is currently not supported. I've forwarded your feedback to the Visual Studio team.
Cheers,
Tanaka
Tanaka_JimhaMicrosoft
When using the Windows Application Packaging Project with .NET Core 3 it creates an app-local .NET Core package which is fully self contained. The single file, is currently not supported. I've forwarded your feedback to the Visual Studio team.
Cheers,
Tanaka
- Hi Tanaka,
Thanks for letting me know about this, I appreciate the response and clearing the air on this question. I hope you have a good weekend!
