Package 2016.1.113

2 posts, 0 answers
  1. jon
    jon avatar
    23 posts
    Member since:
    Jun 2009

    Posted 28 Jan Link to this post

    It's really frustrating and infuriating to use your examples to build 90% of an app, then update to your new release package a few weeks before it's release, and your project breaks because of change made to the nuget package that break even your own example projects.
  2. Nikolay
    Nikolay avatar
    1802 posts

    Posted 03 Feb Link to this post

    Hello Jon,

    Thank you for your feedback. I understand how frustrating a breaking change can be and therefore we are always striving to lower the number of breaking changes where possible. However, in some cases, like introduction of a new feature for a control or other architectural change that will make it more flexible or performant, this can't be avoided. In the cases where a breaking changes are introduced, we put a note about this in our Release Notes in the Changed section for every control.

    Let us know if you have a specific question about a breaking change in regards to your project. We will be glad to assist.

    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
  3. DevCraft R3 2016 release webinar banner
Back to Top