This question is locked. New answers and comments are not allowed.
Hello,
Why Telerik Data Access Visual Designer got deprecated? It was very helpful to do the mappings. Does that mean I will need to type all the code to map my tables?
Thanks,
Dilshod
1 Answer, 1 is accepted
0
Hello Dilshod,
Thank you for contacting us.
The main reasons for the deprecation of the Visual Studio integration are the numerous complaints from our community regarding the issues they experience when automating the builds of their Data Access applications. The details on the subject are described in this blog post. Additionally, the developers that use Data Access benefit more from our powerful runtime features compared to the code generation and we are committed to improving Data Access in this direction.
Regarding maintenance, currently the only option for extending the models and using the latest official release is to convert the .rlinq files to fluent models and to modify them manually through the Fluent API; for the conversion you can use the workflow provided in the former blog post and Data Access Q1 2015.
As we acknowledge that maintaining Data Access models was hurt from the decision to deprecate the code generation tools, I kindly ask you to support the idea about a simple tool that will be able generate fluent models based on the schema of an existing database.
I am sorry for any inconvenience you experienced.
Regards,
Doroteya
Telerik
Thank you for contacting us.
The main reasons for the deprecation of the Visual Studio integration are the numerous complaints from our community regarding the issues they experience when automating the builds of their Data Access applications. The details on the subject are described in this blog post. Additionally, the developers that use Data Access benefit more from our powerful runtime features compared to the code generation and we are committed to improving Data Access in this direction.
Regarding maintenance, currently the only option for extending the models and using the latest official release is to convert the .rlinq files to fluent models and to modify them manually through the Fluent API; for the conversion you can use the workflow provided in the former blog post and Data Access Q1 2015.
As we acknowledge that maintaining Data Access models was hurt from the decision to deprecate the code generation tools, I kindly ask you to support the idea about a simple tool that will be able generate fluent models based on the schema of an existing database.
I am sorry for any inconvenience you experienced.
Regards,
Doroteya
Telerik
Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.