This is a migrated thread and some comments may be shown as answers.

FxCop Erros with version 2010.3.1317

1 Answer 41 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Guenther Stockinger
Top achievements
Rank 1
Guenther Stockinger asked on 23 Mar 2012, 03:05 PM
Hello,

we still use the version 2010.3.1317 of the ASP.NET AJAX Controls and encounter a bunch of FxCop errors (like SealMethodsThatSatisfyPrivateInterfaces or DoNotDeclareReadOnlyMutableReferenceTypes) which does not satisfy the quality department.
Are these errors all fixed in the current version?

1 Answer, 1 is accepted

Sort by
0
Dobromir
Telerik team
answered on 28 Mar 2012, 01:02 PM
Hi Guenther,

We have fixed several errors reported by FxCop in the Telerik.Web.UI code, however, we are not able to cover all of them because majority of the failures come from some legacy code of ours (RadChart for ASP.NET AJAX and the engine we use for our PDF grid/editor export) which has not been updated for quite some time now. Unfortunately we cannot get rid of this code because thousands of our customers use it in their applications and we have very limited options to modify it. Additional set of errors require from us to introduce many breaking changes in our code (class and enumeration names mainly) which will directly affect our existing clients when they migrate to a newer version of our AJAX controls.

Greetings,
Dobromir
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.
Tags
General Discussions
Asked by
Guenther Stockinger
Top achievements
Rank 1
Answers by
Dobromir
Telerik team
Share this question
or