Entity Framework without a database

I like working with the entity infrastructure for many reasons - the ease of use of the entity designer, the power of linq, and the ease of binding. Sometimes I want to create a simple application that does not need to use a database, but still need to work with the data and display it on the screen, in grids, etc. Therefore, I would just like to create a fast EF model and use it for this but it does not seem to work very simply, using it for local data.

My question is: is there any proper use of EF to work with local data, and maybe just serialize / deserialize the entire context into a file? Or is it too much effort to make a job worthy? I used Datasets in this way, along with Linq to Dataset, and it works well ... So maybe this is the best way to go for this scenario?

+5
source share
2 answers

I don’t know what you mean by “local data” for sure (this does not seem to be a database), but I think that part of Datasets vs. EF of your post (for me) is the real question.

EF , -, , Driven Driven Design ..: , Active Record .

, - , , , ( ).

0

All Articles