The attached image illustrates the problem. I'm not seeing this issue with VS2013. It only appears in 2015.
1 Answer, 1 is accepted
0
Nikolay Valchev
Telerik team
answered on 15 Sep 2015, 03:20 PM
Hello Calvin,
Thank you for the feedback and excuse us for the caused inconvenience!
We are aware of this issue, it is logged in our backlog system for further fixing, so you can expect it in some of our next internal builds.
Best Regards,
Nikolay Valchev
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items