Windows 10: Introducing XAML Standard and .NET Standard 2.0

Brink · May 18, 2017

XAML Standard

We are pleased to announce XAML Standard, which is a standards-based effort to unify XAML dialects across XAML based technologies such as UWP and Xamarin.Forms.

XAML Standard is a specification that defines a standard XAML vocabulary. With that vocabulary, frameworks that support XAML Standard can share common XAML-based UI definitions. The goal is for the first version, XAML Standard 1.0, to be available later this year.

Post-specification plans include support of XAML standard in Xamarin.Forms and UWP. You can continue developing your UWP and Xamarin.Forms apps as you do today. When XAML Standard support is enabled, you will be able to reuse and share between the frameworks and expand into more platforms.

To visualize what this support would look like, here’s a side-by-side comparison between today’s XAML in Xamarin.Forms and in UWP:

In the above example – once XAML Standard is supported by Xamarin.Forms, you can use <TextBlock /> and have it supported in a Xamarin.Forms app targeting iOS and Android instead of needing to know and use <Label /> as shown above. In addition to a TextBlock, here are some of the currently proposed items for standardization.

We are at the beginning of a journey that makes it easy for you to reuse your XAML source files between some simple Xamarin.Forms and UWP views. For example – a Settings.xaml page, where you typically have some text, toggle switches and some buttons. You’d only need to design and create one XAML file to describe this UI and that can be used everywhere.

Nothing changes for existing developers – you can continue to use the same APIs you have always used in both frameworks. XAML Standard will help you reuse/share any common UI code that you wish to share between end points.

The XAML Standard v1 draft spec is being defined in the open, we encourage you to start a discussion or give us direct feedback in the GitHub repo here.

.NET Standard 2.0

We are also happy to announce .NET Standard 2.0! .NET Standard is the set of APIs which work in all .NET implementations. A good way to think about it is how HTML5 is today. There are many different browsers which implement HTML parsing and rendering, but the HTML standard is the common glue that holds the web together and allows for interoperability.

.NET Standard was introduced in June of 2016 to bring consistency to the .NET ecosystem. With the .NET Framework, Xamarin & Mono, .NET Core and then UWP, there were many different implementations of .NET and it was very difficult to write code or a library that could work across all of them. Using .NET Standard, and the tooling in Visual Studio, makes it possible to build libraries and NuGet packages that work literally everywhere .NET runs.

The feedback we received on after .NET Standard’s introduction last year was generally phrased as “We like the direction you’re going in, but the set of APIs isn’t large enough to be useful.” The goal with .NET Standard 2.0 is to respond to that feedback and add a large set of .NET’s “greatest hits” into .NET Standard. To do this, we looked at the intersection of APIs between the .NET Framework and Mono. This lead to the 2.0 definition including over 20,000 new APIs and those APIs enable the top 70% of existing NuGet packages to work.

With the addition of .NET Standard 2.0 support for UWP with the Fall Creators Update, .NET developers will be able to share code across all Windows 10 devices, in the cloud and through the rest of the .NET ecosystem. This will also make it easier to reuse existing WinForms and WPF code as many of the most frequently used APIs like DataSet/DataTable, and popularly requested APIs like SqlClient, are now part of .NET Standard 2.0.

You can learn more about .NET Standard here.

Forming the shape of the future

We invite you, the .NET community, to join the discussion and help shape the future of XAML Standard and .NET Standard. You can provide your feedback, both suggestions and issues, at the following locations; .NET Standard on Github and XAML Standard on Github.

Resources:

Github

.NET Standard

XAML Standard

Microsoft Docs

.NET Standard Documentation

Build 2017

Session Video (Presentation Slides)

Ch9 Interview with Tim Heuer, Scott Hunter and Miguel de Icaza

All online Build 2017 Sessions, Presentations and Labs

Click to expand...

Source: Introducing XAML Standard and .NET Standard 2.0 - Building Apps for Windows

:)

johnptd · May 18, 2017

Windows Update installing the same .NET Framework Package

Akheel,

This is not the standard .NET Framework that would show up under Windows Features in the Programs and Features lists. The issue I am having is with the .NET Native Framework associated with and installed in the WindowsApps area. As I mentioned above I
am having the same issue with Microsoft Advertising SDK for XAML app. They are repeatedly showing up together in the Reliability Monitor as being "installed". I had another occurrence on May 29th of these two installing but there is no indication that anything
was changed or added in the WindowsApps folder.

JohnD

Anthony Gal · May 18, 2017

Communication between Standard .NET Component and Windows Runtime Component.

Hi Emilio,

Regarding your concern, this is beyond the scope of our support. To resolve your issue, we suggest that you post your concern on the

TechNet Microsoft forums for advanced troubleshooting and provide you details about your concern.

Let us know the result if you need further assistance.

Windows 10: Introducing XAML Standard and .NET Standard 2.0

Introducing XAML Standard and .NET Standard 2.0

Introducing XAML Standard and .NET Standard 2.0

Introducing XAML Standard and .NET Standard 2.0 - Similar Threads - Introducing XAML Standard

Standard

standard ps/2 keyboard

standard ps/2 keyboard

standard ps/2 keyboard

Standard Ps/2 keyboard

Standard Ps/2 keyboard

Standard Ps/2 keyboard

Microsoft Announces .NET Standard 2.1

Announcing .NET Standard 2.0