Obsolete: 'Please don't touch Calendar property'.

[Phil]

Hi
I am converting to a newest controls and I am getting the following warning:

Warning   2   'Public Overrides ReadOnly Property Calendar() As Telerik.Web.UI.RadCalendar' is obsolete: 'Please don't touch Calendar property'.

This is what it is objecting to:

<Calendar UseRowHeadersAsSelectors="False" UseColumnHeadersAsSelectors="False" ViewSelectorText="x">
</Calendar>

When I go to
http://www.telerik.com/help/aspnet-ajax/calendar-displaying-popup.html
It seems that the property is still in use (maybe the docs has not been updated).  So, how am I to get rid of the warning and keep the functionality.
Phil

[Phil]

Hi:

Ditto on following (they have green line under them):

<TimeView CellSpacing="-1" TimeFormat="HH:mm"></TimeView>
<DateInput DisplayDateFormat="HH:mm" LabelCssClass="" Width=""></DateInput>

Compiler is warning:
Warning   4   'Public Overrides ReadOnly Property DatePopupButton() As Telerik.Web.UI.CalendarPopupButton' is obsolete: 'Please don't touch PopupButton property'.

Phil

[Maria Ilieva]

Hi Phil,

We are aware of this issue which is caused by the affect the RadTimePicker control does not need definitions for the mentioned properties as it does not use them so for some reason we marked them as obsolete in the past. This actually does not break the control's functionality however only  warnings occur when you build the project.
We have forward this to our dev team so they will do the needful to fix this issue.

Regards,
Maria Ilieva
the Telerik team

[Benjamin]

[quote]Maria Ilieva said:Hi Phil,

We are aware of this issue which is caused by the affect the RadTimePicker control does not need definitions for the mentioned properties as it does not use them so for some reason we marked them as obsolete in the past. This actually does not break the control's functionality however only  warnings occur when you build the project.
We have forward this to our dev team so they will do the needful to fix this issue.

Regards,
Maria Ilieva
the Telerik team

 

 

[/quote]

Maria, is has been 2+ years since this issue was identified and it is still happening.  In addition, if you have a global website and are using resource localization you will get 25 warnings for every instance of RadTimePicker....one for each of the properties that are "obsolete":

1. Calendar.CalendarCaption
2. Calendar.CalendarSummary
3. Calendar.CellDayFormat
4. Calendar.ColumnHeaderImage
5. Calendar.ColumnHeaderText
6. Calendar.DateRangeSeparator
7. Calendar.DayCellToolTipFormat
8. Calendar.DaysViewSummary
9. Calendar.FastNavigationNextImage
10. Calendar.FastNavigationNextText 
11. Calendar.FastNavigationPrevImage 
12. Calendar.FastNavigationPrevText 
13. Calendar.NavigationCaption 
14. Calendar.NavigationNextImage 
15. Calendar.NavigationNextText 
16. Calendar.NavigationPrevImage 
17. Calendar.NavigationPrevText 
18. Calendar.NavigationSummary 
19. Calendar.RowHeaderImage 
20. Calendar.RowHeaderText 
21. Calendar.TitleFormat 
22. Calendar.ToolTip 
23. Calendar.ViewSelectorImage
24. Calendar.ViewSelectorText
25. DatePopupButton.ToolTip

All that from the following code in my page:

<telerik:RadTimePicker ID="TmePromptValue" runat="server" Visible="False" meta:resourcekey="TmePromptValue7" >

This is very annoying.  When will it be fixed?

Ben

[Benjamin]

Fyi, this also happens with RadColorPicker for the following 3 obsolete properties:

1. CurrentColorText
2. NoColorText
3. PickColorText

Here is the code in the page:

<telerik:RadColorPicker AutoPostBack="True" runat="server" ID="ClrGridBackgroundColor" ShowIcon="True" Preset="Default" SelectedColor="" meta:resourcekey="ClrGridBackgroundColor1" />

Ben

[Maria Ilieva]

Hello Benjamin,


I'm forwarding again this information to our dev team so that they could take a look at the obsolete properties and modify the control's code in order to prevent such error s to appear in future. I will force the developer responsible for the task to fix this issue as soon as possible.

Excuse us for any inconvenience this behavior may lead.

As a token of gratitude for sharing the additional information for the other obsolete properties you will find your Telerik points updated.

Regards,
Maria Ilieva
Telerik

 

 

[Benjamin]

It has been two weeks, can we get an update on this issue please?  I am not looking to recreate the events that happened in 2012 when you forwarded this same issue to the dev team and we never heard back from you.

[Maria Ilieva]

Hi Benjamin,

I contact our Dev team to check the current status of this case and it appears that all tries for avoiding the mentioned warnings has failed. This is due to the fact that all picker components including the TimePicker are using common base class and these obsolete properties are automatically inherited and marked as obsolete for the specific controls that do not use them.
However when localization files are generated they are generated for all the components and this is causing the presented warnings.
We completely understand that this is very annoying, however the current localization file generation mechanism is using the base Calendar class and this means all components are localized.
Our dev team performed several tries to remove these localization files however this could be done only by deserving the base Calendar class for the different picker components, which could lead to significant breaking changes in the controls functionality.
Therefore the final decision our dev tame came to is that the issues that could appear by such modification are more than the expected benefits.

Excuse us for any inconvenience this warnings may lead.

Regards,
Maria Ilieva
Telerik

 

 

[Benjamin]

Can you ask them to remove the "[Localizable(true)]" (or "<Localizable(True)>" in VB) attribute (see link below) from the deprecated control properties?  That will allow you to keep the deprecated properties, but it will not generate hundreds of warnings (which make it difficult to see the real issues) when we build our site.  Let me know.  Thanks, Ben

http://msdn.microsoft.com/en-us/library/system.componentmodel.localizableattribute.aspx

[Maria Ilieva]

Hi Benjamin,

Unfortunately the mentioned "Localizable" property is set for all the properties in the base class, this means that in case this attribute is set to "false" this will apply for the controls that use these proprieties and they will not be localizable.
Therefore currently we could not use this attribute for avoiding the presented issue.

Excuse us for any inconvenience this may lead.


Regards,
Maria Ilieva
Telerik