Windows 10: Publish WPF App with .Net Core 3.0 on Microsoft Store

KashishGoyal · Nov 5, 2020

Hi All,

I am a Windows Application Developer. I want to publish my Application WPF with .Net Core 3.0 on Microsoft store. I have never done that before so want to know what's the way of doing that. Also how can I regularly update my App on the store.

Thanks,

Kashish G.

:)

Brink · Nov 5, 2020

Announcing Open Source of WPF, Windows Forms, and WinUI

At Build 2018, I outlined our approach to helping you be more productive when developing apps, including the introduction of .NET Core 3.0. We also started decoupling many parts of the Windows development platform, so you can adopt technologies incrementally. Today at Microsoft Connect(); 2018 Conference we shared the next steps – specifically to support innovations in UI:

.NET Core 3.0 Preview 1 adds support for building client apps using Windows Presentation Foundation (WPF), Windows Forms, and XAML Islands.

WPF, Windows Forms, and Windows UI XAML Library (WinUI) are now open source, so you can create experiences with the freedom you want.

.NET Core 3.0 Preview 1 available

As Scott Guthrie announced today, the first preview of .NET Core 3.0 is available. This version of .NET adds support for building Windows desktop apps using WPF and Windows Forms. You will now be able to:

Run multiple instances of .NET Core 3.0 side-by-side on the same computer so you can update WPF and Windows Forms apps to a new version of .NET without updating the entire OS.

Use modern controls and Fluent styling from the WinUI XAML Library via XAML Islands from .NET Core 3.0 apps.

Read about .NET Core 3.0 Preview 1, try out the preview, and give us feedback. The next version of the .NET Framework, .NET Framework 4.8, will include new controls that use the latest browser and media players in Windows 10, support the latest standards, and WPF and Windows Forms apps will have access to WinUI via XAML Islands for modern look and touch support. The .NET Team blog details the differences and compatibility between .NET Core and .NET Framework moving forward.

WPF, Windows Forms, and WinUI ready for your contributions

This journey is our continued commitment to creating the development platform with you, through open source. Our three, popular Windows UX frameworks are ready for your contributions on GitHub: WPF, Windows Forms, and WinUI. Open sourcing these technologies provides transparency between the product team and the community, helps democratize Windows development, and enables the community to engage and contribute to these repos.

We look forward to your contributions. You can get started with Windows Forms and WinUI now. WPF is starting with System.Xaml, with more to come over the following months.
Click to expand...

Source: Announcing Open Source of WPF, Windows Forms, and WinUI at Microsoft Connect(); 2018 - Windows Developer Blog

See also: .NET Core 3 Preview 1 and Open Source Windows Desktop Frameworks - Windows 10 Forums

Tweet

— Twitter API (@user) View on Twiiter

Brink · Nov 5, 2020

Announcing Open Source of WPF, Windows Forms, and WinUI

At Build 2018, I outlined our approach to helping you be more productive when developing apps, including the introduction of .NET Core 3.0. We also started decoupling many parts of the Windows development platform, so you can adopt technologies incrementally. Today at Microsoft Connect(); 2018 Conference we shared the next steps – specifically to support innovations in UI:

.NET Core 3.0 Preview 1 adds support for building client apps using Windows Presentation Foundation (WPF), Windows Forms, and XAML Islands.

WPF, Windows Forms, and Windows UI XAML Library (WinUI) are now open source, so you can create experiences with the freedom you want.

.NET Core 3.0 Preview 1 available

As Scott Guthrie announced today, the first preview of .NET Core 3.0 is available. This version of .NET adds support for building Windows desktop apps using WPF and Windows Forms. You will now be able to:

Run multiple instances of .NET Core 3.0 side-by-side on the same computer so you can update WPF and Windows Forms apps to a new version of .NET without updating the entire OS.

Use modern controls and Fluent styling from the WinUI XAML Library via XAML Islands from .NET Core 3.0 apps.

Read about .NET Core 3.0 Preview 1, try out the preview, and give us feedback. The next version of the .NET Framework, .NET Framework 4.8, will include new controls that use the latest browser and media players in Windows 10, support the latest standards, and WPF and Windows Forms apps will have access to WinUI via XAML Islands for modern look and touch support. The .NET Team blog details the differences and compatibility between .NET Core and .NET Framework moving forward.

WPF, Windows Forms, and WinUI ready for your contributions

This journey is our continued commitment to creating the development platform with you, through open source. Our three, popular Windows UX frameworks are ready for your contributions on GitHub: WPF, Windows Forms, and WinUI. Open sourcing these technologies provides transparency between the product team and the community, helps democratize Windows development, and enables the community to engage and contribute to these repos.

We look forward to your contributions. You can get started with Windows Forms and WinUI now. WPF is starting with System.Xaml, with more to come over the following months.
Click to expand...

Source: Announcing Open Source of WPF, Windows Forms, and WinUI at Microsoft Connect(); 2018 - Windows Developer Blog

See also: .NET Core 3 Preview 1 and Open Source Windows Desktop Frameworks - Windows 10 Forums

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Brink · Nov 5, 2020

.NET Core 3 for Windows Desktop

Intro

In September, we released .NET Core support for building Windows desktop applications, including WPF and Windows Forms. Since then, we have been delighted to see so many developers share their stories of migrating desktop applications (and controls libraries) to .NET Core. We constantly hear stories of .NET Windows desktop developers powering their business with WPF and Windows Forms, especially in scenarios where the desktop shines, including:

UI-dense forms over data (FOD) applications

Responsive low-latency UI

Applications that need to run offline/disconnected

Applications with dependencies on custom device drivers

This is just the beginning for Windows application development on .NET Core. Read on to learn more about the benefits of .NET Core for building Windows applications.

Why Windows desktop on .NET Core?

.NET Core (and in the future .NET 5 that is built on top of .NET Core) will be the future of .NET. We are committed to support .NET Framework for years to come, however it will not be receiving any new features, those will only be added to .NET Core (and eventually .NET 5). To improve Windows desktop stacks and enable .NET desktop developers to benefit from all the updates of the future, we brought Windows Forms and WPF to .NET Core. They will still remain Windows-only technologies because there are tightly coupled dependencies to Windows APIs. But .NET Core, besides being cross-platform, has many other features that can enhance desktop applications.

First of all, all the runtime improvements and language features will be added only to .NET Core and in the future to .NET 5. A good example here is C# 8 that became available in .NET Core 3.0. Besides, the .NET Core versions of Windows Forms and WPF will become a part of the .NET 5 platform. So, by porting your application to .NET Core today you are preparing them for .NET 5.

Also, .NET Core brings deployment flexibility for your applications with new options that are not available in .NET Framework, such as:

Side-by-side deployment. Now you can have multiple .NET Core versions on the same machine and can choose which version each of your apps should target.

Self-contained deployment. You can deploy the .NET Core platform with your applications and become completely independent of your end users environment – your app has everything it needs to run on any Windows machine.

Smaller app sizes. In .NET Core 3 we introduced a new feature called linker (also sometimes referred to as trimmer), that will analyze your code and include in your self-contained deployment only those assemblies from .NET Core that are needed for your application. That way all platform parts that are not used for your case will be trimmed out.

Single .exe files. You can package your app and the .NET Core platform all in one .exe file.

Improved runtime performance. .NET Core has many performance optimizations compared to .NET Framework. When you think about the history of .NET Core, built initially for web and server workloads, it helps to understand if your application may see noticeable benefits from the runtime optimizations. Specifically, desktop applications with heavy dependencies on File I/O, networking, and database operations will likely see improvements to performance for those scenarios. Some areas where you may not notice much change are in UI rendering performance or application startup performance.

By setting the properties <PublishSingleFile>, <RuntimeIdentifier> and <PublishTrimmed> in the project file you’ll be able to deploy a trimmed self-contained application as a single .exe file as it is shown in the example below.

Code:

<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>netcoreapp3.0</TargetFramework>
<PublishSingleFile>true</PublishSingleFile>
<RuntimeIdentifier>win-x64</RuntimeIdentifier>
<PublishTrimmed>true</PublishTrimmed>
</PropertyGroup>
Click to expand...

Differences between .NET Framework desktop and .NET Core desktop

While developing desktop applications, you won’t notice much difference between .NET Framework and .NET Core versions of WPF and Windows Forms. A part of our effort was to provide a functional parity between these platforms in the desktop area and enhance the .NET Core experience in the future. WPF applications are fully supported on .NET Core and ready for you to use, while we are working on minor updates and improvements. For Windows Forms the runtime part is fully ported to .NET Core and the team is working on the Windows Forms Designer. We are planning to get it ready by the fourth quarter of 2020 and for now you can check out the Preview version of the designer in Visual Studio 16.4 Preview 3 or later. Don’t forget to set the checkbox in the Tools->Options->Preview Features->Use the Preview of Windows Forms designer for .NET Core apps and restart the Visual Studio. Please keep in mind that the experience is limited for now since the work on it is in progress.

Breaking changes

There are a few breaking changes between .NET Framework and .NET Core but most of the code related to Windows Forms and WPF areas was ported to Core as-is. If you were using such components as WCF Client, Code Access Security, App Domains, Interop and Remoting, you will need to refactor your code if you want to switch to .NET Core.

Another thing to keep in mind – the default output paths on .NET Core is different from on .NET Framework, so if you have some assumptions in your code about file/folder structure of the running app then it’ll probably fail at runtime.

Also, there are changes in how you configure the .NET features. .NET Core instead of machine.config file uses <something>.runtimeconfig.json file that comes with an application and has the same general purpose and similar information. Some configurations such as system.diagnostics, system.net, or system.servicemodel are not supported, so an app config file will fail to load if it contains any of these sections. This change affects System.Diagnostics tracing and WCF client scenarios which were commonly configured using XML configuration previously. In .NET Core you’ll need to configure them in code instead. To change behaviors without recompiling, consider setting up tracing and WCF types using values loaded from a Microsoft.Extensions.Configuration source or from appSettings.

You can find more information on differences between .NET Core and .NET Framework in the documentation.

Getting Started

Check out these short video tutorials:

Porting from .NET Framework to .NET Core

First of all, run the Portability Analyzer and if needed, update your code to get a 100% compatibility with .NET Core. Here are instructions on using the Portability Analyzer. We recommend to use a source control or to backup your code before you make any changes to your application in case the refactoring would not go the way you want, and you decide to go back to your initial state.

When your application is fully compatible with .NET Core, you are ready to port it. As a starting point, you can try out a tool we created to help automate converting your .NET Framework project(s) to .NET Core – try-convert.

It’s important to remember that this tool is just a starting point in your journey to .NET Core. It is also not a supported Microsoft product. Although it can help you with some of the mechanical aspects of migration, it will not handle all scenarios or project types. If your solution has projects that the tool rejects or fails to convert, you’ll have to port by hand. No worries, we have plenty of tutorials on how to do it (in the end of this section).

The try-convert tool will attempt to migrate your old-style project files to the new SDK-style and retarget applicable projects to .NET Core. For your libraries we leave it up to you to make a call regarding the platform: weather you’d like to target .NET Core or .NET Standard. You can specify it in your project file by updating the value for <TargetFramework>. Libraries without .NET Core-specific dependencies like WPF or Windows Forms may benefit from targeting .NET Standard:

<TargetFramework>netstandard2.1</TargetFramework>

so that they can be used by callers targeting many different .NET Platforms. On the other hand, if a library uses a feature that requires .NET Core (like Windows desktop UI APIs), it’s fine for the library to target .NET Core:

<TargetFramework>netcoreapp3.0</TargetFramework>

try-convert is a global tool that you can install on your machine, then you can call from CLI:

C:\> try-convert -p <path to your project>

or

C:\> try-convert -w <path to your solution>

As previously mentioned, if the try-convert tool did not work for you, here are materials on how to port your application by hand.

Videos

Simple porting case

https://www.youtube.com/playlist?list=PLReL099Y5nRdG-LQ6OZSPECF-eXjgFNrW

Documentation

Simple porting case

Advanced porting case (Part 1, Part 2)

Overview of the porting process

Olia Gavrysh
Program Manager, .NET
Click to expand...

Source: https://devblogs.microsoft.com/dotne...ndows-desktop/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Publish WPF App with .Net Core 3.0 on Microsoft Store

Publish WPF App with .Net Core 3.0 on Microsoft Store

Publish WPF App with .Net Core 3.0 on Microsoft Store

Publish WPF App with .Net Core 3.0 on Microsoft Store

Publish WPF App with .Net Core 3.0 on Microsoft Store - Similar Threads - Publish WPF App

WPF Published to Microsoft Store - App Update Blocked by Running Windows Service

WPF Published to Microsoft Store - App Update Blocked by Running Windows Service

Publish a WPF .NET 8 application to Microsoft Store

Publish a WPF .NET 8 application to Microsoft Store

Publishing an app with obfuscation on Microsoft Store

Publishing an app with obfuscation on Microsoft Store

.NET Core 3 for Windows Desktop

.NET Core Container Images now Published to MCR

Announcing .NET Core 3 Preview 3