Entity Framework Code-First Migration Mistakes in .NET 8 & How to Fix Them 💡

preview_player
Показать описание


#DotNet #AspNetCore #EntityFramework
Рекомендации по теме
Комментарии
Автор

The second issue seems to be more isolated to Visual Studio. Using the command line tools is a lot less forgiving and you get use to jumping into each of the project directories before running the dotnet command. I liked the primary constructor use. Didn't even know it existed and will have to give it a try.

The-Z-Zone
Автор

Awesome to see :D
Thanks again for helping me out with this little pitfall :)

KNPhilip
Автор

Thanks for the video, it was great for me

marceloleoncaceres
Автор

Could you please use word-wrap in your project? Thanks your videos.

engincan
Автор

Thanks.. As a beginner C# programmer, I got trapped with this one myself.. So thanks for explaining why.

AndrewMorison_morrie
Автор

Thanks for this video..
can you help me for that how to secure my API'S with api key..and how to create API key for more security

ojlftlb
Автор

Hi Patrick
Your all video so infomative and i have learn lots, thanks you soo much. I have one doubt related version upgrade. Let me tell you little background, actually i have one existing webapplication which is .net core(2.2) with EF and also used OData service but i want to upgrade that to the latest version. But i am not able to do its showing many error basically its stuck in Odata service routing part, can you please help me on that if possible

anindagiri
Автор

I try this but i try to connect the SQL, bUT IT THROW Format of the initialization string does not conform to specification starting at index 0.

Mrky
Автор

More migration tutorials needed, everytime I follow one of your tutorials the migrations do not work.

stewtech
Автор

awesome :D,
can you make a video for simple chatting app with singnalR using User Identity? please

usamasuhaib
Автор

Thanks, great content :)
Can you make movie how to deploy Blazor Web App on Azure ?

TogetherEver
Автор

I will say the EF team has said don't use the in-memory database provider. 100% don't use it for dev if you are deploying to SQL Server. It's just not the same. You should always dev, test with the same provider you deploy with.

pilotboba
Автор

You shouldn't have the connectionstring in your presentation project. That is the big problem these days.

anomalii
Автор

I'm a little disappointed in you that Udemy courses are not maintained. For example, Blazor stayed on .NET 6 :(
I find it a little bit disappointing that it is not maintained when people buy or purchase the course.

Beji-boy