Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
Today seems a significant announcement from the WinFS team. See here. for details. Changing the delivery vehicle for a component that generated as much attention as WinFS can't have been an easy decision, but given the recent vision statement, I think in hindsight the writing was on the wall.
The main thrust of the news is as follows: WinFS, as originally intended will be scaled back to meld into the afore mention Data Access vision. WinFS is relatively far along and its currents features that fit will be the first to be productized as a core part of ADO.NET vNext. Anything left out will probably be shelved for now...
This is probably a good thing for the robustness of ADO.NET vNext vision, which I think broadly speaking stands to benefit from this, however I have two obvious concerns: what this will do the time lines we expect ADO.NET vNext and whether this will have any other impact beyond supporting the Entities feature. I think it is only natural that this at least imposes some pressure on the ADO.NET time lines, however more interesting is whether this will present issues at the fundamental ADO.NET API interfaces.
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 © 2016, 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 or appropriate markings.