We are sorry to hear that you are having problems with our controls. We do know that the XAML parser gets confused because there are two different classes named LineSeries in the different Chart and Charting assemblies. However, it was not an option to give a different name to the LineSeries in the new control. One can simply use a namespace and not the schema:
It is true that the ChartView is not a control, but it is a set of controls. However, these controls serve the single purpose of visualizing data through a chart display and it has proven convenient to reference the whole set as a single component.
We do not suggest using the old control because of many reasons (limitations due to legacy issues, performance, styling...). Plus, there is a newer version which is much more powerful, flexible, easy to set up and is very very fast. We do not suggest you use both of the controls in a single project because it might lead to compile time and run time errors. Not to talk that someone might get very very confused because of the relatively same names. The new control is set up in a different way than the old one and we know that this might seem a bit unintuitive at first, but this is a different control and one should not expect the same creation notion. Developers that never used the old control become acquainted with the new API very easily.
Here are our QSF examples
where you will find that all examples are used in a data bound scenarios. If you have not seen our SDK demos you can find them here
We hope that you will be able to fully remove the old RadChart from your project and have a great experience with using the new ChartView!
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for SILVERLIGHT.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>