How to create model from existing database in Entity Framework Core - ASP.NET Core

My last blog post was about a feature in SQL Server called Row Level Security Policy. It’s quite simple and known feature for people who’re working directly with databases. But most .NET developers are using ORM of some kind to work with DB, and some of them tend to be blind to stuff that is not available through object model in an easy way. And since Entity Framework is most popular ORM in C# environment and my ORM of choice in most cases, I’ll show you how to use RLS in it.

Artykuł przedstawia co się wydarzy jeśli zrobimy filtrowanie danych przy użyciu metody Contains() na pustej kolekcji w Entity Frameworku.

Kiedy potrzebujemy użyć jakiegoś ORM’a (Object – Relational Mapping) w naszym projekcie, z reguły pierwsza myśl jaka przychodzi nam do głowy to Entity Framework. Dzięki temu narzędziu w bardzo prosty i szybki sposób jesteśmy w stanie skonfigurować połączenie z naszą bazą danych i odwzorować nasze tabele w projekcie. W najnowsze...

Entity Framework (and other ORMs) are in general great pieces of software that makes developers lives so much easier by letting us thinking about objects when we’re working with data persisted in some underlying database. This makes development much easier than writing raw SQL queries. But some of us tend to get too comfy and forgetting about things that lies beneath our beautiful, object oriented code. After all we have Entity Framework, we shouldn’t wrap our heads around SQL stuff. But how about actual...

Generating EF Migrations in .Net Core project can make your day really awful! When you get an error after error, claiming that you did not install the package already present in your project, all you want to do is turn off the PC and go out. But the migration will not generete themself;). I wrote down some solutions for errors with Add-Migration and Update-Database commands.

Zapraszam do przeczytania kolejnej części serii z prowadzenia projektu na potrzeby Daj Się Poznać!

I’m a really big fan of Scott Hanselman and the way he manages his personal/work time. While watching his „soft” talk titled „Scaling Yourself” I was surprised when he described his way of answering some questions coming from all over the world (via email). He said that each of us has a limited number of keystrokes until we die so, it’s such a waste to write a dedicated email with long answer and examples in the code. Why? Because we could optimize that process and share our knowledge with other folks ou...

This is one of those "I had to explain this couple times already so next time I want something I can redirect people to" kind of post. What I want to write about is difference in behavior between using new() and DbSet.Create() for instantiating new entities.

In previous post I've shown how a temporary table can be generated based on IQueryable and then reused in subsequent queries. I have also pointed out a serious limitation. The goal of this post is to address that limitation and touch on unit testing aspect.