The ADO.NET team has released a demo of their Entity Data Model Designer. This tool demonstrates some of the Object-Relational Mapping (ORM) features planned for ADO.NET vNext.
The Entity Data Model Designer allows developers to separate the logical schema from the actual database schema. Benefits include a reduced need for joins in code and the ability to isolate code from database schema changes. Other concepts such as inheritance are allowed
This demo requires the May LINQ CTP and the August ADO.NET vNext CTP.
/filters:no_upscale()/sponsorship/topic/25afca57-6bcb-4c42-9a70-fbea10ce4fc7/MicrosoftLogoRSB-1678874949003.png)
/articles/asp-dotnet-minimal-apis/en/smallimage/logo-1678972581766.jpg){kind=logo}
/articles/functional-dotnet-development/en/smallimage/Fsharp-vs-Csharp-is-one-more-functional-than-the-other-small-1676023056578.jpg)
/articles/dotnet-grpc-json-transcoding/en/smallimage/logo-1674822319367.jpg){kind=logo}
/articles/Dotnet-Seven-MSMQ-Alternatives/en/smallimage/logo-1670585778128.jpg){kind=logo}
/articles/polygot-microservices-dapr-aks/en/smallimage/logo-1666079703389.jpg){kind=logo}
/articles/secure-kafka-cluster-strimzi/en/smallimage/securing-a-kafka-cluster-in-kubernetes-using-strimzi-small-1671647644310.jpg)
/articles/dynamoDB-data-transformation-safety/en/smallimage/logo-1669045832728.jpg){kind=logo}
/articles/rapid-startup-of-your-cloud-native-java/en/smallimage/logo-1680293937095.jpg){kind=logo}
/presentations/empathy-software-development/en/smallimage/qcon-plus-s-1680292453897.jpeg)
/presentations/operationalizing-ai/en/smallimage/qcon-plus-s-1680292123806.jpeg)
/articles/culture-trends-2023/en/smallimage/InfoQ-Trend-Report-logo-1680287660356.jpeg){kind=logo}
/articles/finops-systems-thinking-lens/en/smallimage/12-places-to-intervene-rethink-FinOps-using-a-systems-thinking-lens-small-1679995317220.jpg)
Community comments
ADO.NET vNext
by Jonathan Bruce,
ADO.NET vNext
by Jonathan Bruce,
Your message is awaiting moderation. Thank you for participating in the discussion.
Another milestone in the ADO.NET vNext train -- the Entity Data Model designer prototype has just been pushed to the web. In earlier iterations I have seen, this tool was more stand alone applications, so it's good to see it integrated into Visual Studio directly.
Some early comments:
* I think it will be important for third party providers to understand any additional requirements, beyond the establoshed ADO.NET vNext interfaces in order fully participate with the ADO.NET enity model. Does this tool rely or indeed leverage the DDEX Visual Studio integration mechanism?
* The tool is currently only geared to function with the SqlClient ADO.NET provider, and in my early experiments I've been unable to integrate any other ADO.NET vNext enabled providers. I would be interested to hear if anyone has had success with this.
* The ADO.NET team's policy of a steady drip feed of tools and CTP updates is to be commended! I would also like to see some of the broader feedback too...
jonathanbruceconnects.com/jonathan_bruce/2006/1...