I have a RadDatePicker in which I load SpecialDays with many RadCalendarDay objects. I set the IsSelectable property of many of these to false. When the calendar dropdown is displayed, all dates are properly enabled or disabled.
But in the DateInput the user can still enter and submit one of the dates where IsSelectable=false.
I see all of the dates are in the client. Is there any client-side script that can be used against that data to prevent submission of an invalid date?
If we need to validate on the server, I'm not certain of what the logic should look like. The following code detects the condition but I'm not sure if this is the right way to go about it:
| protected void RadDatePicker1_SelectedDateChanged( object sender , Telerik.Web.UI.Calendar.SelectedDateChangedEventArgs e ) |
| { |
| RadDatePicker picker = sender as RadDatePicker; |
| if ( e.NewDate == null ) |
| return; |
| RadCalendarDay day = picker.Calendar.SpecialDays[ e.NewDate ]; |
| if ( day.IsSelectable == false || day.IsDisabled == true ) |
| { |
| // set picker to invalid state. |
| // display invalid selection message. |
| // stop other processing. |
| return; |
| } |
| // date is valid, OK to continue processing |
| } |
How would we invalidate date picker from the server like that, register a script and force the client to do it?
Thanks.


| Protected Sub RadGrid1_Init(ByVal sender As Object, ByVal e As System.EventArgs) Handles RadGrid1.Init |
| Dim menu As GridFilterMenu = RadGrid1.FilterMenu |
| For n As Integer = menu.Items.Count - 1 To 0 Step -1 |
| Select Case menu.Items(n).Text |
| Case "Between", "NotBetween", "IsEmpty", "NotIsEmpty" |
| menu.Items.RemoveAt(n) |
| End Select |
| Next |
| End Sub |
Hallo,
i have a problem vwith my iis / 2003 Server r2 and can't fix it.
The web application has work with the rights of the user. (user, secret) The user has an account @ the domain and the rights to write an txt file to an folder(other Server)
IIS:.
Integrated Windows authentication + Digest authentication for Windows domain server
.
web.config:
<authentication mode="Windows" />
<authorization>
<deny users="?"/>
</authorization>
<identity impersonate="true" />
The web application can't write the file, but the user has all the rights.
If I write the login in the identity it works fine:
<identity impersonate="true" userName="domainname\user" password="secret" />
