Brief description of the. NET class libraries available in Metro Style

Document directory

•  

From: http://blogs.msdn.com/ B /dotnet/archive/2012/04/17/net-for-metro-style-apps.aspx

. Net is now the core of Microsoft's several platforms, each of which is based on. a specific subset of Net. Many people have come up with a lot of ideas about how to create API coverage.. Net class is available. The PM of the CLR core framework group will answer the question below.

 

The Developer Preview and customer preview versions have been released. Many developers asked about available versions under Metro when developing win8. net class. We also asked ourselves how much code we need to rewrite when porting the code to Win8 Metro.
An available list will be listed later. Here we will mainly discuss some ideas and principles for determining its availability, and the relationship between some. Net classes and Metro classes.

 

Design goals:
Before doing this, we realized that it was easier for developers and technical implementation. The Metro application allows developers to provide some forced end-user experience through all Win8 devices, windows has made a lot of changes and has some influence on our design. The biggest change is that Windows Runtime is a new set of interfaces that can be called by C #, C ++, VB. The task in our group is to make. NET developers naturally call. net and Windows runtime. The Windows runtime group does the same job in the opposite direction. The following are our goals:
Avoid repeated functions in the. NET and win runtime classes.
Clarify the focus of. Net classes
It makes it easy for. NET developers.
Ease of porting C # and VB Code

 

Figure 1:. NET Framework profiles in context

 

Design configuration

In order to design a new class library for Metro, some classes are cut and extended from the existing sub-sets. A chart is used to describe the relationship. In the figure, the circle of small dots is configured by. net, and the intersection is shared. It can be considered that the Metro application is also a subset of the. NET class library and shares some common classes with other subsets. Based on this figure, we select some classes for Windows Phone from the complete. Net class library, because the WP application is similar to the Metro application.

 

Process of selecting a class
To achieve the purpose discussed earlier, we have established a strict selection process. We need to confirm that each API meets the following requirements:
1. Is this API available in Metro? The answer is not obvious. For example, the API of Asp.net is obviously not relevant to Metro development, but the console API may be useful (for example, during testing ). When there are doubts, we should first ask ourselves whether we need to provide these APIs and then remove some unused APIs. For example, path-based operation files in metro are not supported, because file access is called by another Proxy thread.
2. Is this API outdated? This includes poor use or non-compliance with the guiding rules.
3. Is this API repeated with the. NET class? When you use them repeatedly, you have to choose to use them. Generally, they are all made at will. In this way, you cannot share the code well, because you may have chosen different functions. 

 

Is a quantified chart

	. Net for Metro style apps	For Windows Phone 7.1	. NET Framework 4.5
Namespace	72	95	447
Type	1,246	1,788	14,936
Member	15,674	20,291	217,166

 

Table:API surface counts, by. NET profile

For the process to consider, see this article a. Net developer's View of Windows 8 app development.

About porting. Net Code bringing existing managed code into Metro style apps,

. Net for Metro style apps Overview

Converting your existing. NET Framework code.