I thought it could be realized by CSS, but it turned out to be the opposite. Finally, I still rely on JS

//Block the default processing method (prevent the effect of pull-down sliding)
//The passive parameter cannot be omitted. It is compatible with IOS and Android
document.body.addEventListener('touchmove', function (e) {
  e.preventDefault();
}, {passive: false});

ASP. Net core MVC Partial and HTML Renderpartial is an output HTML fragment, but the difference is:

• Html. When partial, the partial view is rendered as a string, which directly generates a string from the view content and returns it, which is equivalent to an escape process.
• Html. Renderpartial is to write the distribution view directly into the response output stream, that is, the current httpcontext. Because it is direct output, it has good performance and little impact. Therefore, it can only be placed directly in the code block, not in the expression, because the return value is void.

For the first time, I found that I can't operate the data inserted into the mobile hard disk, because the Mac OS only supports the reading of NTFS format disk by default, and can't move, modify, rename and delete files

Later I learned that NTFS (new technology file system) is a disk format developed by Microsoft for Windows NT kernel series operating system. Therefore, Apple cannot directly support NTFS due to copyright issues, but this does not mean that it does not support it!

In general, many people will choose to read and write hard disk by using NTFS for Mac and other tools, but these easy-to-use tools are all charged, so I have to find a free solution for the empty pocket.

In the process of developing WPF program, in the page of writing XAML, we can see that many default namespaces in the framework use a section of URL...

Copy these websites in the browser, not all of them can be directly accessed! How are these URLs defined and why can they be used to represent namespaces?

In the process of developing WPF program based on .NET Core 3, there is a need to encapsulate tool classes such as converter and formatter into another class library for reuse.

Therefore, after creating a new. Net core class library, copy the class file into it, and System.Windows.Data will be inaccessible when compiling!

It's strange that the new class library and the framework of the original WPF program are Microsoft.NETCore.App.