Introducing XAML Standard and. NET Standard 2.0

XAML Standard

We are pleased to announce XAML standard, which was a standards-based effort to unify XAML dialects across XAML based Techn Ologies such as UWP and Xamarin.Forms.

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

Post-specification plans include support for XAML standard in Xamarin.Forms and UWP. You can continue developing your UWP and xamarin.forms apps as your do today. When XAML standard support was enabled, you'll be able to reuse and share between the frameworks and expand into more PLA Tforms.

To visualize what the 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 are supported by Xamarin.Forms, you can use <textblock/> and has it Suppo RTed in a xamarin.forms app targeting IOS and Android instead for needing to know and use <label/> as shown above. In addition to a TextBlock, here is some of the currently proposed items for standardization.

We are on the beginning of a journey that makes it easy for you to reuse your XAML source files between some simple Xamari N.forms and UWP views. For Example–a Settings.xaml page, where you typically has some text, toggle switches and some buttons. You ' d have need to design and create one XAML file to describe the this UI and that can is used everywhere.

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

The XAML Standard V1 Draft spec was being defined in the open, we encourage you to start a discussion or give us direct fee Dback in the GitHub repo here.

. NET Standard 2.0

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

. NET standard is introduced in June from 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 is 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 this work L Iterally everywhere. NET runs.

The feedback we received on after. NET Standard's introduction last year is generally phrased as "we like the Directio n You ' re going in, but the set of APIs isn ' t large enough to be useful. " The goal. NET Standard 2.0 are to respond to feedback and add a large set of. NET ' s "Greatest hits" into. NET Standard. To does this, we looked at the intersection of APIs between the. NET Framework and Mono. This leads to the 2.0 definition including over20,000 new Apis and Those APIs enable the top 70% of existing Nuge T packages to work.

With the addition of. NET 2.0 support for UWP with the Fall creators Update,. NET developers would be able to shar e code across all Windows devices, in the cloud and through the rest of the. NET ecosystem. This would also make it easier to reuse existing WinForms and WPF code as many of the most frequently used APIs like datase T/datatable, and popularly requested APIs like SqlClient, is now part of the. NET Standard 2.0.

You can learn more on. 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 S Tandard on Github.

from:https://blogs.windows.com/buildingapps/2017/05/19/introducing-xaml-standard-net-standard-2-0/

Introducing XAML Standard and. NET 2.0