See a small partner asked on StackOverflowCoreApplication, CoreApplicationView, Application, ApplicationView, CoreWindow, Window Their meanings and the differences between them.

So I put together this article.

---

This post is written in multiple languages. Please select yours:

{% include post-version-selector.html %}

Address on StackOverflow:c# - CoreApplicationView vs CoreWindow vs ApplicationView - Stack Overflow。

Namespaces

The full meaning of the classes often need to meet its namespace view, so we need several classes of these full name out of view:

• Windows.ApplicationModel.Core.CoreApplication
• Windows.ApplicationModel.Core.CoreApplicationView
• Windows.UI.Xaml.Application
• Windows.UI.ViewManagement.ApplicationView
• Windows.UI.Core.CoreWindow
• Windows.UI.Xaml.Window

Extra, if you care about the title bar, as well as:

• Windows.ApplicationModel.Core.CoreApplicationViewTitleBar
• Windows.UI.ViewManagement.ApplicationViewTitleBar

Then extra, if you care about the threading model, as well as:

• Windows.UI.Core.CoreDispatcher
• Windows.UI.Xaml.DispatcherTimer

We can see, a large namespace classificationWindows.ApplicationModel with Windows.UI Categories. In other words,CoreApplication with CoreApplicationView Management application model, andApplication、CoreWindow with Window Within management application UI. Small namespace classificationCore with Xaml Categories. In other words,CoreApplication、CoreApplicationView with CoreWindow It is the core management function, andApplication with Window Management of XAML UI.

top down

Application ToWindow To XAML, it is evident until it is able to top-down relationship, comprising the application window, the window comprising XAML content. Then the relationship between them?

CoreApplication A management view of all UWP applications (View), andCoreApplication The view is the direct managementCoreApplicationView; That is to say, UWP applicationsCoreApplication Managing all application viewsCoreApplicationView. And aCoreApplicationView Contains a window and a thread scheduling model, that is,CoreWindow with CoreDispatcher。

▲ UWP application view

InLet UWP application displays multiple windows (multi-view) A paper, since a plurality of views corresponding to the application, it may be more easily understood relationship between them.

CoreWindow We understand that window. For ease of use,Windows.UI.XAML.Window Packaging of this typeCoreWindow。CoreDispatcher Thread scheduling model is based on the message loop, it is because of the news cycle, so this window can always displayed without being destroyed.

External or internal?

We are standing on the perspective UWP ordinary developers to think about this problem, developers are from ordinary UWPMainPage UWP began to write applications. So here, "outside" means that out of the page, or called, those non-XAML XAML content than the content of our direct written; and refers to the "internal" within the page, that is, we usually write XAML content.

External part of aCoreApplication、CoreApplicationView with CoreWindow, Part of a pairApplication with Window. among them,Window is true CoreWindow The package offers more functions related to XAML. here ApplicationView Too, it isCoreApplication The package provides functions related to XAML.

Specifically,CoreWindow With the operating system, the type of application and the whole deal is provided a window such as size, location, status, input set or called;Window Is the type of application and UI within dealing, for example, you can set the UI displayed in the window, set the internal controls which part of the title bar to get inside this windowCompositor. Corresponding,CoreApplicationView Is the application interacts with the operating system, the type of window message loop mechanism working in cooperation, comprising a window region and a non-client area client settings;ApplicationView Type is also dealing with in-app UI, it can use XAML-related types of applications more convenient settings view.

To sum up,CoreWindow with CoreApplicationView Provide more core functions of the underlying operating system or application, andWindow with ApplicationView The former is encapsulated, it enables us to useWindows.UI.Xaml Namespace type in view of the application windows and controls.

More about the application of these concepts

I have some other articles used in these concepts:

• UWP create a program from scratch
• Let UWP application displays multiple windows (multi-view)
• UWP extended / custom title bar

---

Reference material

• Title bar customization - UWP app developer - Microsoft Docs

---

My blog will be starting inhttps://blog.walterlv.com/, And it will be released from CSDN which featured, but it is rarely updated once released.

If you see any do not understand the contents of the blog, please share. I builtdotnet Vocational and Technical College Welcome to join.

This workCreative Commons Attribution - NonCommercial - ShareAlike 4.0 International License AgreementFor licensing. Welcome to reprint, use, repost, but be sure to keep the article signed by Lu Yi (containing links:), It shall not be used for commercial purposes, based on works published after this article be sure to modify the same license. If you have any questions, pleaseContact me。