Breaking changes in RadGridView for WinForms Q1 2008
We at Telerik know that you, our clients, do not like breaking changes. With each release we get complaints that something has changed, even when it as small as a change in the name of a single property.
We understand why you find them dreadful. More often than not software vendors do not speak of them openly and try to hide them at all costs. Often such changes are not well documented. As a result, a lot of time is spent on getting all issues resolved after the upgrade. We know that you are terrified from this process and prefer to use a product, which does not break compatibility with previous versions.
Sometimes, however, “breaking changes” are good. Major changes in the code base, if done properly, allow for better code maintenance. This means less legacy, faster bug fixes, and proper feature implementations. These benefits translate to “more bang for the buck” on your front, where more new features and faster bug fixes matter the most. Finally, if all changes are accurately documented they should not be that hard to fix, which in turn makes live easier to cope with.
The latter is the exact case with the latest release of RadGridView for WinForms Q1 2008. To make the performance of RadGridView top notch we had to reengineer the product and inevitably to implement some breaking changes. This is duly noted [in red color] in the Q1 2008 Release Notes where we have posted a PDF document with an exhaustive list of things that we have changed. A sticky Forum post is due shortly in the RadGridView for WinForms Forum as well. These are just a few of the channels we will use to communicate these changes, because we do not want to leave you alone in this process.
You can review the Breaking Changes in RadGridView Q1 2008 document here:
http://www.telerik.com/products/WinForms/Breaking_Changes_RadGridView_Q1_2008.pdf
We care for you and will do our best to assist you when tackling these issues. In case you find the above document incomplete or hard to follow, please drop us a line and we will help you fix the remaining problems.
We understand why you find them dreadful. More often than not software vendors do not speak of them openly and try to hide them at all costs. Often such changes are not well documented. As a result, a lot of time is spent on getting all issues resolved after the upgrade. We know that you are terrified from this process and prefer to use a product, which does not break compatibility with previous versions.
Sometimes, however, “breaking changes” are good. Major changes in the code base, if done properly, allow for better code maintenance. This means less legacy, faster bug fixes, and proper feature implementations. These benefits translate to “more bang for the buck” on your front, where more new features and faster bug fixes matter the most. Finally, if all changes are accurately documented they should not be that hard to fix, which in turn makes live easier to cope with.
The latter is the exact case with the latest release of RadGridView for WinForms Q1 2008. To make the performance of RadGridView top notch we had to reengineer the product and inevitably to implement some breaking changes. This is duly noted [in red color] in the Q1 2008 Release Notes where we have posted a PDF document with an exhaustive list of things that we have changed. A sticky Forum post is due shortly in the RadGridView for WinForms Forum as well. These are just a few of the channels we will use to communicate these changes, because we do not want to leave you alone in this process.
You can review the Breaking Changes in RadGridView Q1 2008 document here:
http://www.telerik.com/products/WinForms/Breaking_Changes_RadGridView_Q1_2008.pdf
We care for you and will do our best to assist you when tackling these issues. In case you find the above document incomplete or hard to follow, please drop us a line and we will help you fix the remaining problems.
Comments
Comments are disabled in preview mode.
All articles
Topics
Latest Stories
in Your Inbox
Subscribe to be the first to get our expert-written articles and tutorials for developers!
All fields are required