Hi Johny,
Thank you for the honest feedback.
The absence of the designer hurt the usability of Data Access, indeed. We realize that the loss of the code generation left a huge gap in the development process of your applications and makes you question the future of Data Access. In this connection, our intention to improve the runtime of Data Access is very much truthful and very much official; you can find it in this blog post.
Here is the particular text as well:
Additionally, we are considering to ease the situation on the usability side through a simple tool that will be capable of generating fluent models based on an existing database. We will appreciate your support about the idea here.
Thank you for your understanding.
Regards,
Doroteya
Telerik
Thank you for the honest feedback.
The absence of the designer hurt the usability of Data Access, indeed. We realize that the loss of the code generation left a huge gap in the development process of your applications and makes you question the future of Data Access. In this connection, our intention to improve the runtime of Data Access is very much truthful and very much official; you can find it in this blog post.
Here is the particular text as well:
Therefore, we decided to deprecate the visual tooling of Telerik Data Access (which includes the Visual Designer and all Visual Studio integration features), and continue investing solely in our powerful runtime features and code-only (fluent) mapping.Additionally, we are considering to ease the situation on the usability side through a simple tool that will be capable of generating fluent models based on an existing database. We will appreciate your support about the idea here.
Thank you for your understanding.
Regards,
Doroteya
Telerik
Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.