Hi,
I'm working on a migration of a WPF platform from .NET 3.5 to .NET 4.0.
I have met some execution errors that came from a Telerik dll (in fact the dll version was 2.0). So before to purchase a newest version I would like to try if the new Telerik relase has the bug fixed. I have downloaded the newest release WPF 4.0 and I have tried to put into my project.
The good news is that there is no execution error anymore. The bad news is that I have some compilation errors due to HeadererContentControl in my main window (xaml file).
I have to admit that i'm not a Telerik pro user, I didn't know Telerik items and I don't really know what I can use instead of HeadererContentControl.
I have looked for this error and visibly this kind of element was created for your demos if I have well understood and it doesn't exist anymore in the new release.
There is a part of the code where this element is used:
There are errors:
Error 2 The tag 'HeaderedContentControl' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls.QuickStart;assembly=Telerik.Windows.Controls'. Line 142 Position 14.
Error 4 The type 'Telerik_Windows_Controls_QuickStart:HeaderedContentControl' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built.
Error 5 The type 'Telerik_Windows_Controls_QuickStart:HeaderedContentControl' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built.
I would like to add that I had any compilation error with the previous dll (version 2.0) and that these errors have appeared since the migration.
Thanks,
Benoît
I'm working on a migration of a WPF platform from .NET 3.5 to .NET 4.0.
I have met some execution errors that came from a Telerik dll (in fact the dll version was 2.0). So before to purchase a newest version I would like to try if the new Telerik relase has the bug fixed. I have downloaded the newest release WPF 4.0 and I have tried to put into my project.
The good news is that there is no execution error anymore. The bad news is that I have some compilation errors due to HeadererContentControl in my main window (xaml file).
I have to admit that i'm not a Telerik pro user, I didn't know Telerik items and I don't really know what I can use instead of HeadererContentControl.
I have looked for this error and visibly this kind of element was created for your demos if I have well understood and it doesn't exist anymore in the new release.
There is a part of the code where this element is used:
<Telerik_Windows_Controls_QuickStart:HeaderedContentControl Header="title1" > <br><telerik:RadPanelBar><br><telerik:RadPanelBarItem Header="choice1"><br><telerik:RadPanelBarItem Header="choice2"><br></telerik:RadPanelBar><br></Telerik_Windows_Controls_QuickStart:HeaderedContentControl><br><br><Telerik_Windows_Controls_QuickStart:HeaderedContentControl Header="title2" ><br><telerik:RadPanelBar><br><telerik:RadPanelBarItem Header="choice3"><br><telerik:RadPanelBarItem Header="choice4"><br></telerik:RadPanelBar><br></Telerik_Windows_Controls_QuickStart:HeaderedContentControl>There are errors:
Error 2 The tag 'HeaderedContentControl' does not exist in XML namespace 'clr-namespace:Telerik.Windows.Controls.QuickStart;assembly=Telerik.Windows.Controls'. Line 142 Position 14.
Error 4 The type 'Telerik_Windows_Controls_QuickStart:HeaderedContentControl' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built.
Error 5 The type 'Telerik_Windows_Controls_QuickStart:HeaderedContentControl' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built.
I would like to add that I had any compilation error with the previous dll (version 2.0) and that these errors have appeared since the migration.
Thanks,
Benoît
1 Answer, 1 is accepted
0
Hello Benoît,
The Telerik.Windows.Controls.QuickStart namespace is only used within our demo solution. It was created to define a few components that we only use to create a consistent UI in the demo solution we provide. This is why you don't have to use it in your application and instead you can use the native HeaderedContentControl with custom styling if necessary.
Hope this helps.
Regards,
Yana
Telerik
The Telerik.Windows.Controls.QuickStart namespace is only used within our demo solution. It was created to define a few components that we only use to create a consistent UI in the demo solution we provide. This is why you don't have to use it in your application and instead you can use the native HeaderedContentControl with custom styling if necessary.
Hope this helps.
Regards,
Yana
Telerik
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
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 >>
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 >>