Hi Doroteya, I can understand that Telerik wishes to move to a more flexible option for the company and influence how people develop applications, however, the whole point of Telerik's existance from the get go is to provide tools for developers to be able to focus on what they're developing rather than compatibility testing and patchworking tools to work together.
It is quite a task to decide which ORM to go to and at this point in my project's lifecycle, I had already invested a good amount of time customizing the source T4 template Telerik provides us with to generate objects. Now, my entire data layer and strategy is compromised if I want to move forward or I have to keep VS2013 installed only to open the visual designer and update from database and generate code from there.
Generating objects saves and has saved me countless hours of writing objects from scratch and I find it a poor decision on Telerik's part to not have at least one version of their Data Access controls be installable on VS 2015. Being on 2015 would at least give us the time to refactor or migrate to another solution while getting the benefits of the updated VS platform.
With this move, Telerik has cornered it's subscribers who have wholeheartedly adopted Telerik's great set of tools and built their solution on said tools only to have the rug pulled out from underneath them with no options other than sticking with old technology and for once, not because the developers are too busy or lazy to upgrade but because the supplier has decided to not make an extra effort to support a brand new product which will be around for a while.
I've been a longtime subscriber of Telerik's control platform but this move jeopardizes my trust in Telerik as others like me have to go back to the drawing board and review something that we all thought was put to bed and running smooth.
I'd be curious to know how much time it would cost Telerik to build just one version that installs on VS2015 versus the amount of time it'll take me and others in my situation to either convert our process and layer or move to another altogether.
With this post, I hope to re-frame the position Telerik has put us in and seriously reconsider, for the sake of the customers time, building even a single release with the designer for VS2015.
It's great that Telerik looks ahead and stays on the cusp of technology and trends but in the world of software development, processes are put in place and applications need support and further enhancements where it just doesn't make sense to reinvest time figuring something out that has already been dealt with.
Let me, and us, know if there's anything we can do at all to help with the workaround for integrating the designer functionality into VS2015. I'm sure others in the community would be glad to collaborate with me to get this going so we can all benefit, at no cost to Telerik just because we can't afford to stay behind OR to convert our processes at this time.