Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Mike Pizzo of the Data Programmability team at Microsoft has just kicked off what looks to be a very interesting series of articles which will culminate in Programming in the Conceptual Model, or what is better known as ADO.NET Entities & LINQ. Mike has been involved with data access APIs from Microsoft for many years, and has an excellent historical understanding of the thinking that has gone into many of the Microsoft data access APIs. In fact I was able to recently to quiz him 1:1 about about his early experiences in working with the much loved (some might say maligned) Microsoft Excel data access models.
For anyone looking to understand the train of thought that is inexorably leading of to ADO.NET Orcas, I'd recommend this blog entry as an essential reading; and I'll post again when Mike posts subsequent articles in the series.
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.