.Net Foundation Entity Framework Community Standups, 23 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Desktop: .NET Community Standup - July 23rd 2020 - EF Core 5 updates and WPF Roadmap

Description

Join members from the .NET Desktop teams for our community standup covering EF Core 5 updates and WPF roadmap and community engagement.
Topics:
• EF Core 5 updates
• WPF Roadmap and community engagement
• .NET 5 Preview 6 and performance improvements
• Q&A
Links: https://www.theurlist.com/desktop-standup-7-23-2020

A

A

A

All right good morning, everyone thank you so much for joining our desktop community to stand up. I'm super excited to have amazing guests today, so my name is olia garish. I am program manager on dotnet team, focusing on.net, desktop wpf and winforms. I have my co-host dmitry darling with me dmitry. Do you want to.

B

A

B

Sure for anybody that doesn't know me, my name is dimitri lylan and I'm a partner to olia. I work on the xamarin forms team, and.net maui and I also work on lots of xaml tooling for all sorts of developers, including desktop, and I'm just here to be part of the conversation today.

A

Excellent, thank you and we have guests from entity framework and wpf teams. So how about you guys introduce yourselves? Let's start with arthur.

C

Hi, I'm arthur vickers, I'm the engineering manager on entity framework, but I'm at heart. The programmer on entity frameworks still been here for 12 years. Doing that and very happy to show you some of that stuff. Today.

A

Excellent, thank you for joining us. Now we have jeremy.

D

Hi, I'm jeremy likness, I'm a program manager on the.net team and my focus is data, which is a very large focus. A big part of that is entity framework core, but I'm really interested in all the ways.net developers interact with data.

A

Awesome, thank you so much jeremy and we have premolina from wpf team.

E

Hey everyone I'm pramalani david. I am the new pm on wpf, um my team. The desktop ecosystem platform team recently took over the wpf platform and I've been um working on win ui uh all this time and I've been on the team for about eight years and I'm excited about the new investments we're going to be making in wpf.

A

I'm very excited about it too. Thank you so much for joining for rolling here. So today we will be talking about entity, framework and wpf strategy, roadmap etc. But first I wanted to just start it with the new.net5 preview 7 that we just released and are there if you could share the screen. For me, oh perfect, let me go so. This is the blog post by rich lander that got just released, uh announcing dotnet five, oh preview, seven, and if you go down a little bit, there are new things that are included in this preview.

A

One thing that I wanted to highlight is the performance improvements and are, if you click under performance on performance improvement link. Yes, this one. There is a very big and very interesting blog post by stefan that talks about all the performance improvements in dot net, where the dot net file. Sorry so check it out. If you're interested in that area. That's a very, very interesting read, and with that I think we can go straight to entity framework team and hear about all the new things in this area.

A

Arthur yeah.

C

A

C

Okay, so what what the plan is here is uh I'm going to quickly uh show you how you can find what's new in ef core 5, which is shipping the same time as dot net core five in in november, uh then we're going to look at very quickly a just ef core 101, just the if you don't know anything about ef court. This is how it works, and after that, we're going to switch over to jeremy and he's going to show some actual desktop applications, uh winforms and uh wpf uh using entity framework.

C

um That sounds great. If we get time at the air at the end, I might demo a new feature in ef core five, but we'll see we'll see how that goes. So this is uh this is where I live. This is the ef core, github page dot net ef core, and it also is a great place to just get to the documentation. So you can see I'm clicking on the documentation link here, and this is our landing page for all the ef core documentation.

C

If you want to know what we're working on releases and platforms is the place to go, and that will take you to uh what our current releases are, which are lts and all that kind of good information and then under af core 5. We have both here a high level plan and a list of what's new, so in the high level plan. These are the things we're basically doing sorry wrong button.

C

This is what we're doing for um ef core five. uh Many to many navigations uh many to many mappings is uh the biggest feature that we've been working on. uh It's the most uh requested feature on github by over 500 folk, and this basically lets you map two collections together without having to explicitly specify the the join table.

C

We'll just do the join table for you uh underneath uh many too many navigations is another part of that we're also doing tpt mapping, which allows you to instead of mapping different types in your c-sharp hierarchy to a single table. You can map them to a different table. A table per type tpt we have filtered include they'll.

C

Let you filter what you get back from include and split include that can make includes much faster, I'm going through this fast, because, if you're interested, you can go read more on these documentations uh we're also doing some stuff around uh two table and two query to better separate those and then just some general general enhancements down there in uh what's new you'll see lists of all the features that we've released. So, as you saw, we've we've just released preview. Seven, we always release our previews, along with the dot net core previews.

C

That has some features like db context, factory for registering a factory uh for db contacts in di if you're using di ef works, fine with or without di uh resetting the state new pad and photoshop generated defaults. There's a lot of stuff in here and as you go down, you can see in the previous previews we've done things like improved exceptions.

C

We've got community contributions coming in, so you can map ip address directly in your entities. Now lots of good stuff in here so check this out. If you want to see what's new.

A

That looks amazing. Thank you. So much that's a lot of great stuff.

C

So yeah, thank you. So let's go and take a quick look now um at this is like the simplest, ef core demo in a sense, um so I'm gonna just assume that you don't know anything so ef core is a way to easily connect your clr, your c-sharp types to the database, save them in the database. Query them from the database update them the way you fundamentally do that is you create a class that derives from db context?

C

Dbcontext is the class we ship and then you have various options here, but the most common thing is to declare sets of the types that you want to store in the database. So in this case we want to store blogs in the database. So we've created a ddb set property of blogs, and we just put that on our context.

C

Then you need to tell ef what database to connect to. There are various ways of doing this. um You don't have to do it in the context yourself. You can do it externally, but for the sake of simplicity, here I'm overriding on configuring and I'm telling it telling ef to use sqlite. So when af runs, it's going to save all the data in the sqlite database called testdb that are specified here.

C

So that's my context to use it all. I do so if this is a simple console, app jeremy's going to show some uh actual ui apps a bit later. What I do is I create an instance of my context. Now you'll see a lot of examples, especially in asp.net core, where this is happens in a di container and you actually resolve the context from di you don't have to do. That di can be intimidating. It's not necessary for every application, so perfectly valid and fully supported to just renew up your context like this.

C

You do need to dispose it because it maintains the connections to the database, so we need to make sure that those get closed appropriately as well as other reasons.

C

Normally, when you're managing a database schema with the af, you have a variety of choices. You can either have an existing schema, schema in a database and reverse engineer near that to a db context or you can have ef create the schema for you. So what when, if creates the schema for you, it's basically going to look at your the types that you have the blog and the post in this case, and it's going to say: okay, I need an id property. I need an id column for the id heat.

C

I need a name column for the name, property and so on and so forth. You do that with migrations, which allows you to generate a migration which has the sql to update or change the database schema as necessary. However, if you're just doing testing or prototyping or trying stuff out, you can just have ef do that for you automatically. So what I do here is, I assure the database, is clean from last time. I don't care about saving anything, because this is just for testing, and then I create it again.

C

If you look in our documentation page there's a section on testing with ef core. That goes into doing this kind of thing in a lot more detail, so this so basically now we've created a context and we've said told the database make sure it doesn't doesn't exist. The database that we want to talk to so that it's clean to start with and then we said now create it. So it's going to create an empty database with that schema in it.

C

In fact, if we switch on simple logging, which is a new feature in ef core5, you can do a very simple uh log thing in your options, which just says: okay, send the login to uh console writeline. If I run this application you'll see down here when we look at what's happening, some queries from later on in the application, but here we've actually created the table post. So this is what migrations would normally do and we created a table blocks, but this is actually happening here because we called ensure created.

C

So we have a database and then we tell ef okay, I want to insert some stuff into that database, so I'm going to say, add range, which means add a bunch of entities to the database, each blog, I'm creating with a name and then I'm giving it a list of posts. So this will mean that each blog will be related by a foreign key.

C

Each post will be related by a foreign key to this blog in the database, so you're, basically creating this with the relationships and saving them save changes is what tells you you have to actually take these changes in this case these inserts and write them to the database, then you can get rid of that context.

C

You know it's not all the data stored in the database now create a new one, and then we have just this code that print print blogs that will read the blogs from the database also bring back the related posts and then write them out. So if I remove the the logging down here, so we can see the output more clearly, you can see that when we run that it prints out the blog and the post that we saved in the database, so that's basically ef core from uh a no, in a nutshell, a one-on-one!

C

That's what af core does that's what it's for? If there's any questions on that, we can, we can ask them and if not, we can move on to uh to jeremy's uh demos which show win forms.

A

That is awesome demo. Thank you so much. We have one question. I'm going to show you that is for you that says: can you use new c-sharp syntax for using brackets context without brackets.

C

Absolutely yeah, I don't I'm not doing it here, because I have two blocks see I have one using block and another using block there. If I were to remove this actually, then I could very easily just go here and change it to the new syntax, like that, and everything would be fine.

A

Excellent, thank you so much and we have some comments about wpf. Thank you so much guys for that, keep them going. We will talk about wpf after entity framework, but please post, I read everything and I will read it down the read it out loud for primarly all right. So now I think jeremy. Do you want to share something with us.

D

A

Excellent, let.

D

Me let this pull up, so one of the things that we're very focused on moving forward is ensuring that the experience for ef core is first class across different platforms, and so what I'm going to show you here is building on what arthur shared, and this is a window winforms app.

D

So it's a windows desktop app targeting netcore 3.1 and it's using entity framework to create a ui to build this, and I want to show you just some of the pieces, so I've defined a very simple category, so there's a category and a name and notice, I'm using a observable collection list source. So this is something that's provided by entity framework core to handle the two-way data binding. That's inside of winforms app. So, instead of having to cast or build your own proxy, for example, this will automatically do all that change tracking for you.

D

Similarly, we have a product that references back up to a category, so this is a navigation property. So if I have a product I can navigate into the category and what's nice is this is set up to lazy load, so it'll basically pull back. One of the entity sets and only load the other one if you access it my product contacts. This is what establishes my connection to. The database shows categories and products we're using sqlite and again.

D

This could just as easily be sql server, but to keep the example simple and self-contained I'm using sql lite because it just creates a local file and I'm using these lazy loading proxies. These are what detect, when you're, trying to access a navigation property and pull them in. So that is all it takes for me to set up my database portion of this.

D

If we go into the form, I made a very simple form and I'm kind of showing why I'm more of a developer and not a designer, but I've got categories at top products and a save button here, and if we look at the code behind for this, I've basically got my product context.

D

When the forms load, I create one, I'm making sure that database is created now, unlike arthur's, I'm not starting fresh each time, so I'm not deleting it and creating it. I want persistence between sessions, I'm loading the categories and then I'm just using a binding source so that data source right here uses this entity framework extension method to turn it into a binding list.

D

That's pretty much! It we've got our save button that validates and calls save changes and then refreshes the views. So let me go ahead and run this and show you what the experience looks like give it. A second here should pop up shortly. So now I have my fancy form and I'm just going to do some categories. We'll do food we'll do water, that's okay! I didn't spell it right, we'll do dessert and then for water.

D

Actually, let's make this drink, let's do a couple drinks we'll do soda we'll do water we'll do shake and then for food. Let's add a couple entries we'll do pizza and burrito and then we'll save it, and you can see our ids populate. We can navigate back through these. Let's go into the drink, let's say we don't want water too, healthy, save that and now you can see that we've round tripped and updated the database.

D

So that's the winforms experience and really what I'm trying to show is just how straightforward it is to be able to build a context and wire it into your winforms app now. Having said that, another example of a platform experience is wpf.

D

This is a wpa, oh.

C

Go ahead interrupt you. Can we go back to the winforms app and and talk? Can I have a few things I want to? I want to mention um that's possible. Yes, that is.

D

So very impossible.

C

So uh one thing that uh jeremy, uh one thing that jeremy mentioned is how the ids were populated automatically. So I think it's useful to understand what af is doing under there and kind of the best practices with ef.

C

So you really don't want to manage your primary key and foreign keys yourself and here, if you want to use these navigation properties like we saw with blogs and posts and with categories and products uh in jeremy's example, where you connect them up and then you let af generate the ids for you and in fact it's not ef, that's really generating the ids, it's the database. So what happens when af saves those things to the database is that it asks them to the database.

C

S is asked to generate a key for the new inserted row, so this is like a sql server, identity, column or other databases have have similar, and then the database then sends that back to ef and then ef knows that's the new id it connected up to all the foreign keys and everything before saving those, and so, in effect, what you end up being able to do is manage your object model without worrying about the the keys and the foreign keys at all, which I think is one of the big advantages of ef and if you find yourself in af having to worry about those keys, then probably take a step back and ask yourself why?

C

Because it's often easier to it's easy to get into a state where you're not sure what you're doing and you just set keys and things and then you're really fighting against df rather than working with it. um One more thing I want to point out if you can go to the the main designer page.

C

This is the code behind.

C

Yes, there so um scroll down to the initialize.

C

I know the form load, that's right. The form load so there's a couple of things that are going on here that are interesting in terms of the data binding scenario. So the ef context, when you query, or you attach things or add them to the context, it starts tracking the state of those entities. So it knows what values have been added. What values have changed and can do automatic database updates?

C

What we're doing here is when we do context categories load that is apparently we've gone to build context. Category load is loading into the context all of the categories in the database and then, when you connect the binding list to it.

C

That means it's going to feed those changes that you make in the app back into ef and because af is already doing that tracking of changes when it sends the update to the database, it's only going to update the things that have actually changed so there's a very tight connection, tight integration here between what you're changing in the ui and the things that are marked as tracked in the database, so you can very easily just say right. I've made all those changes. Do the update?

C

Those are the two things I wanted to talk about.

A

D

And the wpf app should be pretty easy to show, because if we look at oh, I did I close my wp. No, what am I doing? This is kind of funny net core app, okay,.

C

So this is my wpf yeah.

D

Yeah, and so this is a netcore app three one we can see. I designed it similar, although I I learned from prior experience and moved the save button here. That was my design decision, but I do want to show that product is the same.

D

Category is the same, and our product context is the same, so exact same setup. I could easily have this in a shared library that I share between my wpf and my winform application. If I want to do that this time in the code behind for the main window, I've got my product context and then in the xaml. Let's uh show xaml here one second in the xaml I've defined some resources here. I've got two collection view sources.

D

One of them is the category and the design times having some issues, but that doesn't keep it from working and running. The second basically takes the products and binds up to the category, so this is showing products for the currently selected category.

D

Then we've got our regular data grids and our save button so we're doing a very similar thing, I'm basically when it's loaded, I'm ensuring the database is created. I'm loading it only this time, I'm using the extension method to observable collection, because wpf uses the notify property change. So it's going with the observable collection instead of the binding list source, but that is the only real change here when we click the button.

D

We save the changes entity framework core is smart enough to understand that I've modified a field, maybe changed the name that I've removed the field, I've added a field and it will just gather those changes and push those out to the database and then I'm just refreshing my grid and then at the end of it I'm disposing everything. So let me run this and show you what that experience looks.

D

Like and I love this hot reload by the way with wpf and the designer, I was literally working.

C

D

As as I was designing these these um grids and fields, so let's do food, drink, dessert, we'll come up to drink, we'll do water, soda, shake kombucha and then we'll save that and same thing. We get ids for all of these. We can navigate off the food to drink. Let's say I decide, I don't want the shake I'll highlight this row I'll, delete it I'll, save it and entity framework core has removed that.

D

So that is what I wanted to show. Is these two experiences now our documentation right now has get started: scenarios for console apps for asp.net, core apps and for um xamarin we just added xamarin.

D

These reference projects will be added to getting started for win forms and for wpf and we're also working on blazer, both server and web assembly. So we should have a complete list of documentation here over the next few weeks. That covers end in scenarios across all platforms.

A

Perfect. Thank you so much jeremy.

C

So if there are.

A

C

If there, if there are questions on the on that, we can, we can ask those um if not I'll, go back and show uh my uh ef core5 app, which demo, which shows index of properties a new feature. Okay,.

A

So it was just about to ask about that. So go okay!.

C

Let me share again.

A

C

Okay, so we're back in exactly where we were before this is where I left off before jeremy started. um Now we could, if we wanted, to let's say, extend this model. We could add a new public. Sorry, if I can type.

C

um Let's say we want a created time so we'll create a date time property created on I'm, making these all just public properties with getters and setters. You don't have to you- can use read-only properties, initializing them in constructor and all that kind of good stuff. That ef nef will still understand and be able to do that. So I can do this and I- and I can now start using this- I could add things here to date times and everything, but let's say I'd ship, this application to a customer and they wanted to.

C

Actually I was shipping it as a library rather than application, and they wanted to extend the library previously, of course, one of the limitations was you had to be able to modify the actual clr type in order to add a new property to it. So, even if you could modify the database to add a date time created on column, if you weren't able to actually change the clr type, then you couldn't get that new column in the database.

C

So you could do that by allowing people to extend the types you know derived from the mag columns and stuff and if in f, core 5 we've made that easier by allowing indexer properties. So, instead of being defining this directly as a date time I can put in here a index of property for see, I might have the code snippet.

C

Yes, so, rather than write this all out live, let me just post this on there, so you can see the change. So what I've done here? uh Sorry I've, I'm supposed to do it in my post and I've started to do it in my blog. So let's do it in the post, where I was supposed to do it in the first place.

C

There we go so what I've done here is I haven't added any specific property. I've added a backing field of a dictionary. um This is just a string to object. You don't have to use two objects. If you know you're always throwing strings, it can be strings of string. If you're, storing against you can be string queen string to object, lets you store anything and then I've added an index of property on here.

C

So this is an index of property where, if I pass it a name, it's going to try and get that name out of the dictionary or set that name into the dictionary. So I can now pass this. uh You know the to the to the other application developer and take this out of my library. uh They still have to tell ef um how to that there is a property that they want mapping in there, um which is done in this model builder.

C

This is the fluent way to map entities, so we can do entity post here and then we can tell it. It has an index of property. So this is what I would do uh so because we have that index of property on the actual entity type. I can now say: okay. What I want to do is I want to store a date time in that and call it created on now. This doesn't require me to change my post type at all, so any any application can extend this and just say: add this index to property.

C

So we've done that if we now run and create the database, what we'll actually see hopefully, is that it creates a property for that when we create the database, so I'm running with the logging on again: oh, it didn't failed, but it still created the database because I haven't updated this rest of the code. Yet so you see in the database now we've got created a column. It's text in sql, like in sql server, you'll, see date time 2 by default.

C

Sql lite has a very limited type system, so date times are stored as text by default. You can change that in efcor. You can tell it to store them in different formats and it will, but you can see that, even though we don't have that created on property in my post class, because we have an index of property and we put it in here, we now have that index property in the in the in the database.

C

I could replicate this line and do another one I could say: okay, we also want a modified on, for example, and that's fine. That code will work. I want to show a quick tip here that a lot of people seem to miss, which is you don't have to repeat yourself. Quite that much. You can do this, what we call the the nested lambda syntax, where I take these things- and I put the first one in here and then I can also do another operation on the same entity type.

C

So, instead of me having to type the entity type post twice type, do this sorry do entity post twice there? I've only actually done it once and then I'm saying okay, I could do lots of operations on that, so it's kind of a shortcut rather than have doing model, build.entity.post.property model, builder, entitypost.property and so on. Over and over again for the rest of this demo, I only want indexed property, so I'm going to remove that and this will still work, but you can go to the other syntax.

C

Obviously, so we can actually now initialize these properties. We can do this index of property syntax, so I can say okay, I want to put created on I'm going to save created on here, and I want it to be date time now.

C

Okay, so we'll do that for all of these, we'll just all of the entities that we're inserting we're now going to insert it created on daytime now.

C

Okay, so hopefully, when I run this, it won't, uh it won't crash this time because we're actually saving things into the properties. Indeed it didn't. So what you can see here is on the insert, so it's doing insert values into post block id and it's using my created on and if you, because I put sensitive data on me by normal by default, ef will not output in any of the logs any of the values from your database, because that could be sensitive data. However, when you're debugging, it's very useful to see those.

C

So that's why you have this enable sensitive data logging, if I went to the top of here, you'd, see a warning in the log saying that we've got this on, but what we can see is the actual parameter values here are the parameter values for date, time now and those are actually being stored into the database.

C

I didn't read them out yet, but if we go to our print blogs, it's very easy for me to just add in here, create it on and then do post created on. So I can now get this out of my entity just by accessing the index of property. I could do that in a query.

C

To I could say where created on is greater than this or less than that, and that would still work, and uh when we look at the output of this, if I run it again, we now see that the output down here we have the the created ons being accessed from the index property. So that's something that we're putting in ef core 5.0. It's primarily there because this is actually the way many to many work under the covers.

C

We effectively create entities that are dictionaries that have the information that you're in so that they don't need to be specified, but because we built this in a kind of uh componentized way, you're free to create your own index of properties and use them in your own way, which can be very useful if you want to extend existing metadata in this way.

A

C

A

Perfect, thank you so much for the demo that looks very exciting and we had a few questions, but we already had answers in the chat, so emily were asking about. Crap templates uh and jeremy responded that we have tutorials all right, then arthur. If you wanna, stop sharing the screen. Yep.

C

So I will do so follow.

A

You guys again all right uh alex is asking. I mean crap example in the templates of the wts.

B

Template studio, I guess.

A

B

Templates windows templates do.

A

C

ah I'm not aware of anything.

D

I think I've I'm familiar with that. That's like some add-on templates. I think they're.

B

Yes, so windows.

D

B

Studio, it helps you create new projects in visual studio that are wpf uwp. I think there's potentially xamarin support, but basically it's like a nicer file, new project experience that has complex features. You can integrate mvvm patterns using prism or some other library, for example, so that your your new project has all that built in. So I guess that's the form of the question right folks on the chat that uh it'd be nice to have a check box to start adding entity framework capability. There yeah.

D

B

D

Yeah we we have some really great templates for asp.net, core and and even asp.net, but having those for desktop experience is definitely something I think would be great.

B

Yeah so clint rodkis is the pm. He'd, be a great person to chat with jeremy. If you guys have ambition, sounds good all right. Thank you. Chad, good question.

A

I have another question from gintura a question for wpf with informs biden if database is slow in response, because network or disk speed wouldn't that block the ui. Since it's not async.

D

So, in the the spirit of very simple demo examples, I I used a synchronous connection, because it's a local sql light, but entity framework core exposes all of the asynchronous methods. So there is a save changes, async and a load, async, etc.

B

Right, yeah in any real world app that has those kind of concerns. um Definitely we we should architect to the technology. I think for if the demo was perfect even like, I would build a simple app since sql light is local. Some of those concerns are not there. Unless the sequel light itself becomes really big or complicated.

D

But it's good to put a note on the beginner documentation about that. So thank you for that feedback. Yeah.

A

Thanks right, are there plans to make that net core able to compile via llvm.

B

Nope, nobody here talk about that.

D

Yeah, I was gonna, say great question for the compiler team.

A

Yep, could you mix identity and wpf.

D

That is a great question. I just think my identity, I think identity server for authentication.

C

D

C

D

C

We we've uh we've shown some some of that in the past. I don't think we have any current samples. I don't know who's tried it recently, but we can follow up on that, because we should show how to use that awesome.

A

Perfect, thank you guys for all the questions and keep posting the questions. You can always go back to entity framework, but meanwhile, I think we can transfer to wpf for millennia. Go ahead.

E

Take this out sounds good and julia. I guess you are going to be projecting the page.

A

E

um So as julia gets started, folks to show you the roadmap once again, I'm pramalini david, I'm a new pm on wpf, uh my team, the the developer ecosystem and platform team recently took ownership of um wpf. We are the same team that also owns win, ui uh and react native, and uh so now a single team owns all of the ui frameworks and invest investments that go in there uh and we are going to be ensuring that there is consistency in the different investments made across the ui frameworks.

E

So with that, let's take a look at the roadmap. All right.

A

Actually, I think I will have to ask someone.

D

Yeah I can help who else.

A

To share it so oh.

B

If you could, I'm on it.

A

There's too much of a software going on on my machine, no problem! If you could go to wpf github repo great there, you go.

E

Yes, um so dmitry, if you'd like to zoom in um ever so slightly to the table on the page sure um so folks for um fiscal year, 2020 2021, uh my team is committed to the investments that you see in the table: investments in wpf, so starting off the first one framework servicing fixes um into.net core 3.1 and net 5..

E

This is something that was started by the earlier team that uh owned wpf and when my team took over we're essentially continuing on that work, and this is ongoing work and and it will go on um through the year. The next one is ongoing integration with net5.

E

We have done most of the work, I want to say, um maybe about 70 of the work, so we will have this done and wrapped up fairly soon, um as we get closer to wrapping this up. I will refine the target delivery column in this table to indicate when exactly this is going to be completed.

E

Number three on this list, building out test infrastructure, to add tests to validate and merge community prs now. This is something that we have heard from you, the community loud and clear, and uh we are actively working on making this happen so that we are able to um enable the community to contribute directly merge pr prs directly once we have our test suites available publicly.

E

So this is a heavy duty investment for us we're working on this in 20 h2. We already have a dedicated developer for this. For this particular work item um the fourth one on this list is accessibilityupdates.net 5..

E

Now there are certain accessibility um bugs as well as features that we need to add in order to meet the um government stipulated accessibility guidelines in the various countries where your your apps run, and this is something that is a priority for us and we are going to take this up in um 21 each one and the last item there, but not the least, is arm 64.

E

uh As you are aware, uh we microsoft is investing in new devices on 64 devices and uh we look forward to having your apps running on those devices and therefore wpf arm. 64 support is an important one for us and we will. We are going to be taking that up in 21 h1 as well. uh Once again as we get closer to the uh preview timelines, I will be updating this table uh with more refined target delivery dates.

E

I will be also sharing that same information with you on calls such as this, um so please stay tuned.

E

So now, if we want to scroll down a bit to dimitri, I would like to talk about our sla for the plethora of github issues, good issues that we have now for all new issues that are filed after july 10th. We have a sla of 72 hours. That is three working within three working days. We will triage those issues, however, that does not mean that all of the good issues that were filed prior to july 10th will would not be looked at.

E

In fact, um we have a team of uh um developers come pm who are actively triaging the the 500 or so issues that are currently on github uh to bring those counts down. So you will see questions coming back from us on the issues that you may have filed earlier.

E

We come back to you with um questions clarifications about a certain issue and um that will that will show you that we're actually actively trying to bring our accounts down on that front uh in terms of the pull requests that you have submitted now we are committed to selecting at least one or two prs per month to merge into the framework.

E

Now the criteria for selection of a pr is the bulleted list that you see there um I'll read it out. It's recency. um The next is the extent of reactions which may be likes comments um the thumbs up. You know, hearth, sign so on and so forth. The next is fixes to existing issues. um That is it's not a new feature. It's an existing feature.

E

um The next is complexity of the fix in itself, um then we have breadth of the impact of the fix how um widely uh it is going to be impactful to the apps in the ecosystem. Today the next is low potential for regression. um The next is has adequate test coverage. um The potential for regression is also tied to the adequacy of test coverage that we have, and the last one is that it's not a new feature request.

E

Now it does not mean that if you have filed appear for a new feature that we would not consider it, the only thing is that at the moment, for the moment, with our current uh number of resources, our team is committed to the list that you see here as the months go by and as we are able to better resource and staff, our team, uh we do expect this list to get refined a little more, at which point we will be able to accept new features.

E

We also expect that our test suites would then be available publicly to you and you would be able to merge prs directly. um The next topic I wanted to touch to is about the non-code prs. These are um documentation bugs documentation issues now the sla for um this, too, is um 72 hours for all new pr's filed after um july um july 2020.

E

um The next one community calls so we I do expect to be on community calls such as this at least um every other month. I will also be on the win ui community course giving you updates on the uh progress of the work uh in the investments that you saw in the roadmap. In addition, we are definitely looking forward to your questions, your feedback on the investments that we are making.

E

So I do expect to see you all on these community calls every every other month last, but not the least resourcing um the resourcing topic heavily influences the um extent and the depth uh and breadth of the investments that we make in wpf. uh Our team's management has approved um the additional resources that our team needs.

E

It just so happens that this global covet pandemic has caused our hiring to be slower than usual, and so as we combat this pandemic together and more specifically as we overcome this pandemic together, I do fully expect that our hiring hiring will get back um to speed and we will be able to hire the required resources for our team for this project and as and when that happens, we will be refining the roadmap with the investments, probably newer investments, some additional investments that we could make for the coming fiscal year.

E

That brings me to the end of the roadmap and I'll hand it back to olia, or you know I. uh I would love to answer questions from folks on the call.

A

Sounds great, thank you so much for melina and we got a lot of questions and you did a great job already answering them. So there were questions about the staffing. uh Is someone working full time on wpf uh people were asking to explain why uh prs were blocked for the last year? I don't know you already talked about it. If you want to add anything to that go ahead. If not, we can go through other questions.

E

um Nothing new uh that I haven't already mentioned again. We we just took over wpf. uh I won't be able to speak to um what the earlier team did or did not do, but now that we have taken over do expect that you will hear from us. um We we have a team uh with limited resourcing, but we are uh 100.

E

Whoever is on the team is 100 on this project um and- and you will be hearing from us on the github repo.

A

All right, thank you and.

A

There were some questions about milestones: how does the sla related to microsoft? What automatically closing issues due to no recent activity, if not shouldn't you remove or rename the milestone? To avoid confusion?

A

Sorry, the old wpf team has marked some issues with the milestone 5-0. What is the current target for the 5-0 release? Are you still using that milestone as a guideline.

E

That's that's a good point. We as we triage the issues and the prs we are adding some additional labeling that is not um camouflaged in some internal uh terminology, um so I am going to actually revisit um the label about about the milestone five and make sure that it's more descriptive. um Apologies that between the earlier team and and our team, we haven't really um have an opportunity to look at the labels. Look at the milestones and scrub them correctly, but we'll get on top of it.

A

Perfect. Thank you. There was a suggestion from shar fujin for entity framework core to suggest, stored procedures executed in ef, core jeremy and arthur will take a look at that.

A

C

Store procedures is a is a a big area. um You can definitely call store procedures. um We've improved the mapping in the f core five uh there's still some more work to be done in that area, but um you can use them.

A

Perfect yeah and they get a command about that after a year of silence, any goodwill enthusiasm for community engagement has faded. It's good that there will now be someone running the project, but the fact that it was abundant without any communication for so long is satan on the project. Staying on the project yeah, unfortunately, and uh morgan nielsen is here. Yelling at us just merge my pr's. They work they work.

E

Getting there getting their martin getting there, you are you loud and clear, and I have your list with me as well: no tasting.

A

Is needed for martin.

E

A

By default, all right um any more questions guys go ahead. He tested.

D

A

Yeah it worked on his machine.

D

Ship it compiled yeah.

A

uh There were kudos to telerik, and I want to join that. That is amazing control, vendor and our dear friends. We have a bi-weekly calls with them for bin forms and they do absolutely amazing job their greatest people. I had a chance to meet them in person when I was in the conference and yeah. It's a pure pleasure working with these guys.

A

Alright, any more questions.

A

Let's give it a minute and if not, I think we can.

C

A

A day how's, the weather, for you guys for melina, I know you're in india right is.

E

Yes uh and it's surprisingly, cooler than usual um less traffic on the roads, less pollution, and so it's it's really nice uh outside the the only difference. It's it's completely dark outside it's night time. For me, um it's it's! It's 11 30 in the night.

A

Thank you so much for joining us that late wow, that that is a neat one thanks. We really appreciate that and alex has a command. I hope microsoft.expressions.drawing will soon be open sourced as nuget package.

B

Yep, there's there's no plans to work on that at this time.

B

uh How is win ui and and uh matt, and that net maui looking to align uh it's a you know early days for both projects, I would say: stay tuned, we'll have more more on that when we're ready.

A

And yeah I've heard the request to put priority on assembly load context, issue 1700. That is nice number. Thank you for the feedback.

A

All right is any: one of us is familiar with crypto api, as it is kind of crosstalking.

C

A

Well, that really depends what you can ask the question and then we can find answer or find the person who is familiar. You can tweet us or send us email.

A

A

A

So microsoft expression, drawing alex is asking: will it not be available for net core to retreat.

B

Yeah, I'm not aware of anything happening with that assembly at this time.

B

If, if there's desire to make something available that you know the ship is part of blend previously to.net core, I would say: file a vs feedback ticket is probably a good place to start.

A

And I saw earlier there were questions about webview 2, so w2 is supported for winforms and wpf nwpfor.net, core and dotnet framework. I posted the link. We have a docs on getting started for winforms for wpf. That is the link, but right there. You can also find getting started for bin forms as well, and that is a new chromium based controls. We are very excited to have it.

A

All right so that question: why is x, 509 certificate, 2 finalizer, not clearing up crypto containers?

A

I don't know we're. Gonna have to find.

D

Someone for that one.

A

But we'll try to find someone all right.

A

I think that is it for today. Thank you so much everyone for participating. Thank you, our dear guests, for joining us for melania for joining in the middle of the night. We really appreciate it and super excited about new wpf uh road map strategy.

A

Hopefully we'll get all the pr's merged, especially dot morton, because he yells the loudest and.

C

A

Excited about all the news in entity framework core world, thank you, jeremy and arthur for joining us and you're. Welcome thanks guys, keep your questions.

C

A

I will see everyone in the week. Oh in the months, have a good one. Bye, bye.

B

Bye. Thank you. Bye.