Thank you for the reply, and the benefits you listed are nice, but not an overwhelming argument, because now, your customer base doesn't know what you will do next to hobble our development. You and the rest of the folks at Telerik seem to be missing the point. We, as developers, are not so much questioning your decision, but we are questioning your SUPPORT of your customers, after making the decision. Not to mention this is MORE than just getting rid of the visual designer.
I need a tool, that will take my domain model, INCLUDING the naming of assocations (because the default naming is often insufficient), and generate a fluent model from it. It doesn't have to be perfect... just SOMETHING... ANYTHING...
We also do extensive work with WCF and the T4 templates you USE TO HAVE are now gone, and there are no T4 templates for a fluent model... why not? Now, not only am I forced to MANUALLY recreate my model, I have to create my own T4 templates because you simply took away a feature. That's EVEN MORE work I have to do... because of your decision.
I have been a DevCraft license holder for several years... since before you made Data Access a free product, so to me, you should have communicated what you were planning to do better for your customers, especially customers that have been with you for several years. We COULD HAVE provided feedback about what we need before you made this transition... had time to create the tools to help your existing customers that have PRODUCTION deployments of your products.
But instead, we're left with an almost laughable solution of "Stay on Visual Studio 2013, and keep using this one version of Data Access". Not only can I not take advantage of new features of Visual Studio 2015, I'm stuck with any bugs discovered in this version of Data Access, and get no enhancements to the product, because we're stuck... with no real help from Telerik.