You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a WPF app App1 (.NET 6 with <TargetFramework>net6.0-windows</TargetFramework>) and my client would like to distribute it through MS Store so I created a Windows Application Packaging Project and add reference back to App1. Everything works well and we can publish our app except with just a Hello World project, the package size is more than 60MB (for neutral arch).
I understand it is due to it packing the whole .NET 6 with it. Is there a way to publish it using framework-dependent model instead? We don't mind user being asked to download and install it if they don't have it already installed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a WPF app
App1
(.NET 6 with<TargetFramework>net6.0-windows</TargetFramework>
) and my client would like to distribute it through MS Store so I created aWindows Application Packaging Project
and add reference back toApp1
. Everything works well and we can publish our app except with just a Hello World project, the package size is more than 60MB (for neutral arch).I understand it is due to it packing the whole .NET 6 with it. Is there a way to publish it using framework-dependent model instead? We don't mind user being asked to download and install it if they don't have it already installed.
Beta Was this translation helpful? Give feedback.
All reactions