Answer the question
In order to leave comments, you need to log in
What is better to use for working with databases in WPF?
I ask for advice.
After working with WinForms + ADO.NET with datasets and dataadapters, I started coding in WPF.
The question arose of the most optimal work with the database on MS SQL.
All examples and articles on the net refer to various ORMs such as LINQ to SQL or EF, but since I am writing an additional module in third-party software and I have to work both with my own database and with directories from third-party databases, it is somehow scary to use ORM. I could not find an adequate example for working with third-party directories or what to do if the database structure changes.
I will add that the amount of data in the database is quite large, as well as alterations and improvements to the code in the future. There are no problems with writing code in SQL.
I need advice, "brain reduction" and links to read.
Answer the question
In order to leave comments, you need to log in
WPF and databases do not have a single point of intersection.
So you can use absolutely any way to store data, even manually making sql queries, even using EF \ NHibernate.
As for hibera, I can say that changes are quite easily supported, in semi-automatic mode, you can add / delete columns and tables.
you can continue to work the old fashioned way, and so is EF, given such a thing as bindings in WPF
It might be worth taking a look at your "Custom" ORM, tailored to your goals, objectives, and components used.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question