.Net Foundation On .NET, 1 Oct 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Migrating EDMX projects to Entity Framework Core

Description

What’s new in EF Core 3
https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-3.0?WT.mc_id=dotnet-c9-cephilli

Porting from EF 6 to EF Core
https://docs.microsoft.com/en-us/ef/efcore-and-ef6/porting?WT.mc_id=dotnet-c9-cephilli

EF Core Power tools
https://marketplace.visualstudio.com/items?itemName=ErikEJ.EFCorePowerTools&WT.mc_id=dotnet-c9-cephilli

Migrating from EF 6 to EF core
https://channel9.msdn.com/Shows/On-NET/Migrating-from-Entity-Framework-6-to-Core?WT.mc_id=dotnet-c9-cephilli

Many projects have used the EDMX files and the EF Designer to generate their models with Entity Framework. However, Entity Framework Core has not added support for EDMX generation. So what do you if you want to port your EF projects to EF Core?

In this episode, Entity Framework PM Diego Vega joins Christos to give us a thorough walkthrough of porting an Entity Framework EDMX model over to Entity Framework Core

[01:06] - Why would I want to move?
[03:18] - Reviewing a sample EDMX model
[08:10] - Porting the hard way
[09:29] - Porting the easier way
[13:44] - Using the EF Core Power tools
[18:24] - Exploring inheritance

#dotnet #entityframework #dotnetcore

A

Hey guys, we're here with diego.

A

On this episode, we're going to be talking about migrating from.

A

Entity framework with edmx to entity framework core. join us.

A

Hi, everyone., my name is christos and we're here with diego once again to talk about entity, framework goodness and migrating to entity framework core.

A

So we had diego last time and we talked about migrating from.

A

Entity framework 6 to entity framework core using a code-first approach.

A

yeah., but I think we left one big part over there,, which was migrating edmx-based projects into entity framework core,, which is normally a states kind of migration, right?.

B

That's right., so we have many, many customers that are using the ef designer., so they have basically an xml file that contains the definition of.

B

The ef model in their product and the steps to migrate to ef core, if you are using that different.

B

So we wanted to explore that in more detail., okay. now,. Why should I want to move??

B

So the reason you may want to move to.

B

Ef core is because you want to take advantage of the new features.

B

We keep investing on ef core on adding new features.

B

And new functionality that are new, performance,, better performance..

B

If you want to take advantage of all of that,, especially on.net core,, then you probably want to be on the modern version of the ef core.

B

Got you. now,? Is it used to move?.

A

Like, is it a straight to run a file and everything upgrades or run a different upgrade?.

B

Not always., I mean,, it depends on how much code you have,.

B

How many entities you have, and the complexity of the model, and what features you are using., so we're going to look into some details. Today, like what happens if you have inheritance and if you have many-to-many relationships,, which are features that ef core doesn't support. Yet.

A

B

So we're going to see that it doesn't completely matter.

B

Because the way the database looks like when you have those features in ef6,.

B

We can map to that database using ef, core.

B

right. the code and your entities are not going to look the same..

B

I think the other thing we're discussing prior to this was also.

A

That there are scenarios where people who have invested in ef6,.

A

Edmx-Based scenarios may not want to move at all if they are happy with their database, right?.

B

That is true., so the big thing that we have been.

B

Doing lately with ef6 is ported to.net core.

B

A

So in .net, core 3.0,.

B

You are going to be able to run ef6.

C

B

That means that if you have an existing application, that has been working with ef6 and it works well,.

B

Basically, you are happy with the performance and you're happy with the set of features that you have in ef6,.

B

Then, instead of moving to ef core,, you can choose to just stay on ef6 and move to .net core anyway.

A

Perfect., so you get the benefits of .net core 3.0 without you having to do any code changes, so you minimize the risk? exactly.

B

Perfect., you may still need to do some code changes for different reasons,, but the idea is to minimize them.. That's the keyword.

B

fantastic. excellent. now, would.

A

You like to show us how it should be: done?, actually, yes,, let's go with the demo, right?.

B

Yeah. I wanted to show first,.

B

There is a page in the documentation here.. If you go to the docs.microsoft site under ef.

B

Right. there is this port to ef core page.

B

And documentation that we are going to update.

B

Actually,, we are planning to point to this videos that we are recording today and the one that we recorded last time, and we're going to complete this information with all the new information about ef6, and .net core,, and many steps that we are exploring. Today.

A

Yes. also, we'll have the code from today and the previous episode.

B

Yeah., I have to add a link to the repo.

B

We're going to have all this code. we'll make sure we add it to the description.

A

So, as you look at this video, make sure that you check the description to find all the information and the links to the document and repo, right?.

B

That's right. demo time.

A

Okay., so let me show you.

B

This is basically an edmx file that contains the definition of a model. perfect.. I have in blue, like three entities that are from the same model that we discussed last time..

B

There is an issue tracker., basically a very simplified version of an issue tracker..

B

It has a repo table,, an issue, table, comments. Table., then there is another table that is the user. That is basically linked to all of them, because users can create repos,.

B

Users can be assigned to users,, and then I added something that I didn't have on the.

B

Code-First version that is inheritance., so this enhancement is basically a type of issue.

B

That is mapped to the database using a strategy called table. Prototype.

B

This means that there is a table for.

B

Enhancements that, in this case only contains.

B

The id of the issue and a new column that is vote.

C

B

Basically, because issues are contained already.

B

All the information that is common between issues- and these are entities bugs.

B

all right., but I want to have additional information for enhancements.

B

for instance, enhancements, have people voting for them because they wanted this feature, and bugs have reprosteps that enhancements. Don't have.

B

C

So I wanted to show that detail. Here.

B

Okay., this is a very simple application,, more or less the same thing I had last time.

B

I have some code.. I am going to just walk through why we debug, through everything that we're doing on this application.

C

Okay., so this is.

A

Running the application, as is with the old edmx-based solution?.

A

B

Perfect. yeah. so, first of all, I have some code here that is cleaning up, because I want to start from scratch.

B

Now I have this api that I call to just create the database based on that model, and it works with edmx the same that it works for code-first.

B

Now,, I start adding some data., so I'm going to add myself and one of the engineers on the team,.

B

And I'm going to add a repo,.

B

Repository,, an issue that, in this case, is.

B

An enhancement that is considered ported to.

B

Ef core- and it has one vote.

B

Now, I'm going to add some comments. basically, are we done yet? yeah. okay.? I save this and then I have some other code that executes the query..

B

Let's say I want to query for the repos, where the name is.

B

Portef6Toefcore- and I want to include who created it.

B

I want to include also what issues it contains, and I'm using the syntax that include supports on.

B

Ef6 to include the issues and the assignees of that issue.

B

I wanted to show also there is a relationship here between issues and user.

B

There is basically the assignees and it's a many-to-many relationship. got you.

C

So it has like asterisk on this side and asterisk in this side.

B

That means that there are two collections pointing to each other on the model.

B

I execute this and I basically have a method that shows that on the ui.

B

my ui is just text..

B

I could make this a little bit bigger..

B

I guess if I can do that, quickly, that will be great.

B

I just show that I have an enhancement that has.

B

One vote and the common data.

B

For an issue and people that are assigned to that issue and the comment.

B

So all that code in the right is basically using this feature or the pattern matching on c#.

B

So if this issue happens to be an enhancement,, then I'm going to show the information from an enhancement that, in this case, is the number of votes..

B

If it is a bug,, then I'm going to show the reprosteps,, but all I had in the database was an enhancement.

B

perfect.. This is just a bunch of loops that are iterating all the data in that query..

B

So the idea is how to make this work on ef now.

B

Let me tell you,, there are two options in theory.

B

Okay. so one is,, let's say that you have invested a lot of time trying to make the property names in your model prettier than the names of the columns in the data.

B

Let's say that you have been working with the legacy database and your column names.

B

Are awful and you don't want to.

B

Have the property names in your entities with the same names? You have renamed a lot,, then there is a lot of value in the code that you already have in.

B

Your edmx and the code that the templates generate from the edmx.

B

So you have c# classes now or db classes that are based on those pretty names that you chose,.

B

And you don't want to lose that. sure.. So if you are in that situation,, probably the best option is to take all those code files with the classes and move them somewhere else in a different product, maybe or just copy them in the disk,, then remove the edmx and bring them back.

C

And start creating all the mapping and.

B

All the additional code that you need to create in order to remap.

B

Those entities to exist in database.

B

Okay. but that's going to be complicated. yes., so there is another option. That is what I wanted to show today,, which is basically ef core.

B

I didn't mention it today,, but I think we mentioned it last time.

B

it doesn't have a designer.

A

It only has a code-based experience.

C

That is correct.

B

So basically, you use code-first,, but you don't need to think about code-first or you need to write the code-first and then the database gets created..

B

Code-First is all about having a code-based experience.

B

Yeah., so the database can exist.

A

And you can get the model from an existing database.

B

Yes., it's only like that model,. The way it works is called code-first., so we reverse-engineer the database.

A

To generate the code-first code, more or less, right?.

B

That's right., so the first thing I'm going to do,.

B

I need to do a bunch of manual steps. Here,.

B

And I hope I'm not going to make any mistakes because then it's going to take longer., but the first thing I want to do is uninstall ef in this project.

C

Okay., so this is.

A

Removing the nuget package of the older md.framework expression.

B

That's right. perfect., so I removed it.

A

B

Now,, the next step is basically I want to get rid of this edmx file.

B

yes., so this file was interesting because it contains some things that I customized.

B

got you. when I reverse-engineer an existing database,, I'm never going to get the inheritance.

C

I actually did that manually, here.

B

Right., but here I'm going to still get on ef core or something that is very similar, and that allows me to work with those tables.

B

right.. So let me do that.

A

So, in this case, we're not keeping any of the old designed generated files.

A

And we're blasting everything, we're starting from scratch.

B

Yeah,, that's correct. you're, going to see that now I have.

B

My code in the application that I basically had everything on the program cs- file., it's not going to compile because all these initializers don't exist anymore and this namespace doesn't exist anymore in this product because I don't have the package anymore.

B

sure.. So I could delete this. But now you also have two options.

B

One is to basically do it all by hand and go manual.

B

Sounds painful. so the first thing I'm going to do is install package and I'm going to install.

B

The equivalent package that is entity framework core.sqlserver because we are using sql server.

B

Sure., that's going to bring a bunch of dependencies that are like.

B

Small dlls that I need to run ef core on.net framework in this case., then the next package, I'm going to add, is the tools.

B

For business tool here so that you can do the same kind of.

B

Migration commands and we added the common line command that.

B

Is to basically reverse engineer the database integrals first.

B

So the next package, I'm going to replace this with just tools.

B

So once I have this installed, there is a command that is scaffold,.

B

The contexts that I want to show.

B

It has two options that I would need to use in this case.

B

One is say, connection, and here I need to pass the connection string and then the other one,.

B

I can use dataannotations.

B

Basically, this is telling the co-generation that I.

B

Prefer to use dataannotations when it's possible to do the mapping, otherwise,. It needs to make more calls through an apis [inaudible] first to get the same. Result.

B

The other thing that is mandatory is the provider.

B

So basically here I want to use this provider and that's basically the name of the package that I installed before microsoft.entity framework core.sqlserver.

B

So that'll work., but I want to show something that is easier.

C

If you are using visual studio., there is a community project that is.

B

Called the ef core power tools., that's driven by one of our mvps..

B

There is eric aj.. He has been active on the ef space for a very long time.

B

And he's doing many things that are very useful.

B

In this case, we have a ui basically to create this model, based on the data.

B

very nice., I'm going to right-click on the "project".. I go to ef core power tools..

B

Here, I'm going to say, "reverse engineer.".

A

So, first I need to select the connection.

B

This one is actually pointing to the database that I want.

A

Does this come from your application, package?.

A

App config? is it picking up [inaudible].

B

I actually naturally fit does that or if it remembers the last things that you do it.

B

A

Anyway,, I am going to create this again.

B

This is the normal name of the local db server that you have installed with visual studio and I'm going to pick the database here.. It's tracking.

B

I'm going to go to our next step.

B

here. It shows me the list of tables that I have,.

B

There's a new version in ef core 3.0.

B

You are going to go to select not only tables, but also views.

A

But this is using the ef core 2.2 still.

B

I'm going to add also some other options: here.

B

So the name of the context name that this is going to generate,.

B

I'm going to correct this casing: here.

B

The namespace is basically the namespace of the application.

B

I don't need to change the product path., I'm going to add this option to pluralize or singularize..

B

That basically means if there is an issues table on the database and the names are in english,.

B

Then this is going to run some code that is going to find the work issue that it's a singular and it's going to name the issues as issue instead of issues.

A

Okay. just to be clear,, this is a ui on top of the command line, right?, so anything that you do here is also available through the command line?.

B

It is., but on the command line,, some of the things that this tool can do take a lot of work,.

A

Like, for instance, the singularization,.

B

We need to plug in a singularizer in your code before you run the tool.

B

A

Yeah., so this is great-. This is making our life a lot. Easier. yes. fantastic.

B

The option to use dataannotations or to prefer dataannotations is here, and discuss another option which is use handlebars.

B

Handlebars is a toolkit based on templates to cogeneration.

A

So when you check this option,.

B

I'm not going to use it today,, you get a handlebars template in your app..

B

So if you want to customize the output and you want to customize what code gets generated, you can modify. The handlebars template.

B

is very similar to t4.

B

yes., I'm aware., but it's different,. It's similar in concept, at least not necessarily how [inaudible].

A

Templating stuff, nice. yeah.. It tells.

B

Me install the ef core provider package in the product., so that means I then really need to do that before, but I did it already, so I'm just going to leave it out.

A

Doing everything for us. very nice.

B

Yeah. okay., so let's run this.

B

Model generated successfully..

B

If I look at what it generated here,, it basically added the entities that I.

B

Wanted and it added the issue tracking context.

B

So mostly, what I had in programs now should be fine.

B

Okay., so this namespace doesn't apply anymore, because this is the namespace for ef6.

A

So I'm going to delete that and I'm going to replace it.

B

With microsoft.entity framework core, which is.

B

The main namespace for ef core., these apis, don't apply anymore.

B

In ef core, we have ensuredeleted and ensurecreated.

B

If you want to do the same thing,, these are mostly the same.

B

But there is a change in what at returns,.

B

At returns, a dv entity entry now in ef core.

B

So if you want to get the entity, back again,, you have to do [inaudible] entity..

B

We did the same thing on the code. First version,.

B

Same for this one, same for this one,, and for this one.

B

But there are a few more channels that I need here.

B

So this is the first big change., so on the ef6. Model, enhancement was an entity that derived from issues.

B

So all the properties from issue were there.

B

yes. in this new model,.

B

I switched from using inheritance to use composition.

B

So basically enhancement. now,. If I look at the code,, it just represents an entity that is associated with.

B

An issue, but it only has the id,.

C

That is its own primary key, but also acts as.

B

A foreign key to the issue and the votes.

B

So basically, there was a restriction that we had before that doesn't apply anymore..

B

So in the previous model,, an issue could only be either a bug or an enhancement.

B

Yes., so if it was an enhancement,.

B

It was impossible for it to have repo steps,, and that makes sense.

B

Yeah., but if it was a bug,, it was impossible for it to have bots and that doesn't totally make sense.

B

So it depends on what you are trying to model from the real world.

B

But sometimes, inheritance is not the right way to model things.

A

Sometimes, for instance, one thing that you may.

B

Want to build to do is to mutate, the type, to say okay, this person that used to be an employee,.

C

Now I want this person to be a customer.

B

Right., the only way to do that, if you are using inheritance, is to delete the employee and create a new customer with the same identity basically..

B

So this other way of doing things, actually, allows you to say, "oh,. This thing can be two things at the same: time.".

B

Because basically,, you are using composition now and the aspect of it being an enhancement, can.

B

Be added to the basic issue and then the aspect of it being a bug,.

B

Can be added as well. if you decide that something that you thought was a bug, it's actually an enhancement,.

B

Then you can change it without deleting it., so there are some advantages of this way of doing it.

A

At least for this scenario helps us model closer to the real world case, rather than being restricted by the functionality of entity. Framework, perfect.

B

That's right.: it really depends on what you're modeling.

A

There are things that really.

B

Match what inheritance does very well,, but there are other things that don't.

B

so in this case, the aspect that is.

B

Not so nice is that we're going to have to change the code.

C

So here we need to add an issue actually,.

B

It's not an enhancement anymore., it's just the base class., because the base class is the one that has almost all the properties..

B

But there are a couple of things that you're going to see here. That don't still show will lines because different reasons.

C

Let's go to the first one.

B

So on issue, we have.

B

Some things that didn't get generated exactly the way we wanted.

B

So one of the conventions of the reverse engineering that.

B

The ef core does is that when it doesn't fill out the name of the navigation poverty very well,, it just takes the foreign key.

C

And appends they word navigation to it.. So this is not something that we really want in the model.

B

So I'm going to just rename these to createdby,.

B

Which is what I had before.

B

the other thing that I don't like here, for instance,.

B

I have id navigation here, but I'm not going to go into renaming everything because it would take a long time.

B

This other thing that changed here is,.

B

Well,, that was a many-to-many association.

C

So it was a collection of assignees,.

B

A collection of users that were assigned.

B

And I cannot have that anymore, because ef core doesn't support many-to-many., so I need to have the link table here: mapped to an entity.

B

So this is actually assignments now.

B

Because it's assignments,, then I need to create a list of assignments.

B

Sorry, not exactly that kind of assignment.

B

Now,, these two people are actually users.

C

So I need to create a new object.

B

That is assignment and say, "okay,, the user, for that assignment is divega and new assignment user.".

B

Well,, I said username,.

B

But I actually meant to say- okay,. The reason I cannot do user is because there is another property that got name differently from what I would want in the assignment entity.

B

So I have this username navigation.

B

Yes. that I just want usually user.

B

so I'll rename it, and I go back to this code,, so I can assign it directly.

B

I'm missing, I believe, one of these.

B

New bracket? yeah. yes., then votes shows we will [inaudible] because votes is actually a property of enhancement.

B

So what I had to do here is basically remove votes from the issue,.

B

And create another entity., so I'm going to say var enhancement equals to contexts.

B

This got generated for me, automatically.

B

yes.. The enhancements are now also get their own property.

B

Yes., I say add, and the new enhancement,.

B

And then I can add the two things here.

B

So one is,: I need to relate it to the previous issue.

B

yes., so the issue there is actually I need to rename it,.

B

Is issue, and the votes was one, right?.

B

Yes. okay,, so I need the semicolon here., let's go rename this as well.

B

This is an issue.

B

okay,, so I'm fixing the parameters..

B

So now we have many-to-many replaced with a link table,.

B

And we have the composition instead of inheritance for enhancement. perfect.. This one is also one that needs renamed.

B

Yeah. so let's go to the next one.

B

The one that is wrong is this one.

B

Now,, let me do it.

B

So now I need to think about what to include,.

B

And that things have changed a little bit., so this one is one that needs to be renamed as well.

B

So let me go to, in this case,. It's a repo class.

B

I could have just search and replace all the things that.

B

Were not named correctly to the right thing,, but I didn't do it. so that one is now okay.

B

Now,, I need to use a different syntax here..

B

We look at this when we did the code-first version as well.

B

So to do this, multilevel include,.

B

There is a new method that is called theninclude.

B

So basically, you replace that pattern. Would theninclude.

B

We said before that there are no more assignees directly.

B

So this is an assignment,.

B

And there is another,, then include here, because I actually want to bring the user that is behind that assignment..

B

So for an assignment, give me the user, that's behind it.

B

Maybe I made a mistake: here.

B

the type of, yeah,, it's an assignment,, multiple assignments..

B

So there is that in, for this one,.

B

I need to do the same thing,, because the syntax with the nested select doesn't work on ef core.

B

I believe I need to include a couple of things: more.

B

I'm going to do that later. another thing that changed between ef 6 and ef core.

B

This .local is no longer an observablecollection..

B

I have a toobservablecollection method,.

B

So I can satisfy the signature of the next bind method that takes obervablecollection.

B

So this code that I had here that just switch on the type.

B

Doesn't work, anymore. doesn't work anymore.. So what I need to do is actually say something like issue.enhancement is not null,.

B

Then I'm going to print information about it.

B

Yes. so in this case, I would do something like issue,, sorry, enhancement, votes,.

B

And now something can be,.

B

An enhancement and divega at the same time., so I'm just going to add another if that says,, if issue bug is not null,.

B

Then, let's print the information about the bug.

B

An open, curly, brace,.

B

And this is an issue that the bug aspect of it.

B

Okay, so now this is the same thing that we are.

B

Talking about before, this now assignments.

B

So it means basically now I need to go.

B

To rename this and say,.

B

Well,, the name of the user is not directly on assignment..

B

You need to go one property more.

C

The user same for the full name.

A

B

Almost there., so there are a few things that I remember. I need to change on the context that we generated.

B

Okay., so all this code, compiles.

B

But when I generate the code using this ef core power, tools,-.

B

Okay. -this doesn't include a connection string, anymore.

B

C

So temporarily, just to make it work and to.

B

Show that I can connect to that database,, I'm going to add it. Here. do not do this in production. yeah., so your sql server is the way to do it,.

B

And here I can do.

B

B

It will use double, because this is c sharp.

B

B

I missed actually the keyword here.. This is the server.

B

Now,, the initial catalog,.

B

The database is going to be issued tracking,.

B

And I'm going to do integrated security.

B

A

Yeah, true, and semicolon.

B

Okay., so this should almost work..

B

Let's try to see what fails and we'll go from there.

A

I say it'll runs.

B

I think it may run, but it is going to miss.

B

Some information, because I didn't include everything that I had before.

C

B

So this is taking a little bit to compile and run.

B

Let's step through. one thing I want to do: actually.

B

I'm going to comment all this code that deletes database and create database and fills it because I want to show that I actually can connect to the same database that I created before., very good point.. I don't want to delete this.

A

Yeah. for now., let me go.. This is a bit slow, surprise.

B

I think I can comment all this code.

B

Maybe my calibration don't match anymore.

B

Yeah., I need to comment this one too.

B

Yeah. okay., so I just went to run the query and see how it works.

B

So it's compiling and running.

B

This should have connected to a database already unless something went. Wrong.

B

Okay., so there are a few things that are not.

B

Needed or have the wrong names of the properties here.

C

So on the assignment property,.

B

There is an inverse property attribute.

B

For the navigation property user., so let's go change. Those.

B

The problem is that when you rename properties,.

B

All the strings don't get renamed.

B

okay. in this case,. I think that it would be okay to remove.

B

Was it this one?.

A

The one you complained about?, I don't know.

B

User. yeah. okay. foreign keys, name,.

B

Inverse property, assignments, yeah.

B

So let's see what else comes up.

B

Okay. similar error, created by an entity that.

B

Navigation issues are not pointing to each other.

B

Okay. inverse an issue.

B

Let's get rid of those.

B

Yeah,, this one, for instance, is wrong, basically.

B

I'm just going to delete it.

B

The user, going to issues, yeah.

B

If I go to user.

B

When some of these are probably not named correctly.

B

Okay. now, this seems to be okay..

B

Let's try again. until we get rid of the things that are wrong.

B

Since I'd seen the earlier pixel,, you have to start.

B

Oh,, I didn't stop it last time.

B

I guess,, let's put a breakpoint here.

B

Let's just run the whole program.

B

Yeah. this one is complaining about inverse and.

B

Created by type issue.

B

Maybe that's the one they were complaining about. Before.

A

Yeah., I think you want to remove that.

B

B

I forgot to remove that.

B

So this attribute is useful when you're not.

B

Doing fluent configuration for your relationships because it allows you to say very quickly, "hey, by the way,, the navigation property, that's pointing on the other direction. Is this one.", this navigation property assignments on type user is not valid.

B

I think that it would be probably things would work if I just get rid of all of them, but let's try that.

B

Brute force. yeah.

B

I want to recognize that this is a little bit painful,.

B

That is a manual process.. It is. there's no direct path.

A

For upgrading and we recognize that,, but at least we give people a way of migrating if they need to migrate, right?.

A

B

Here you go. it works. okay.. So what things are missing now in the data that I'm showing?.

B

Let's see., so we have the assignees and we have the comments,.

B

But we don't have anything about the counts of votes.

B

Exactly., so the reason is basically now that's a separate entity and I didn't include., so I wrote code to actually say if this one is null or not. Null,.

B

Basically, print this,, but I didn't include it so it's always null.

B

So include, basically,. I need to start also on the issue.

B

Then I'm going to say then include basically for this issue,.

B

Go to the enhancement aspect of it.

B

Yeah., that should be sufficient for us to get the data.

B

For the data that we have in the database.

B

okay., so if I run this again,.

B

Let me change this a little bit. Bigger,.

B

Now it shows that the votes are [inaudible].

C

B

A

In less than 20 minutes.

A

all right. yeah., I mean it is painful, as we recognize that,.

A

But now that we have steps on how to do it,.

A

And there's documentation that explains how you can go from edmx to ef core,.

A

I think people can weigh their challenges and they can weigh the risks of doing that.

A

Then,, if they feel that the benefits are odd, way,, the effort of manually migrating to that,, then it's worth taking doing the migration.

A

I hear you. it's something that you need to personally look at and then identify the need for the migration,.

A

But I like now that we have both a code-first approach.

A

And an edmx approach on going to ef core.

A

That's right. perfect. well,. Thank you very much for your time.

B

You're welcome., thank you for this opportunity. for your demo, and thanks everyone for joining us.