Hello, I just installed windows 8 pro and VS2012, and I have a problem with your scheduling components (12.1).The steps to reproduce the problem are very easy:
1) Create a new WPF application (Net Framework 4.5)2) Drag and drop a ScheduleView
Roberto Dalmonte
We have the same problem with this control. Any news on the bug fix?
Can infragistic tell us a rough estimate on when this can be fixed?
This issue can be easily replicated in their WPF Sample projects. Hence I am surprise that this is not picked up in their testing
Hi Yanko,
Any news on this yet? it is already November
I'm pretty sure the latest official service release included the fix. Also, I think latest updates to .NET 4.5 from Microsoft also resolved the issue.
Hello,
The Service Release is already out. You can download it from our website -> Account -> Select the product -> Select ‘Service Release’ tab.
Thank you for your patience.
I downloaded the patch and now started getting another issue.
I am using the following code, which works fine on C# 4.0, but throws an error on C# 4.5
<ig:ScheduleSettings.WorkingHours>
<ig:WorkingHoursCollection>
<ig:TimeRange Start="00:00" End="00:00" />
</ig:WorkingHoursCollection>
</ig:ScheduleSettings.WorkingHours>
"Add value to collection of type 'Infragistics.Controls.Schedules.WorkingHoursCollection' threw an exception."
I need to set the "End" value greater than "Start" Value, then it works fine.
A zero duration TimeRange is not valid for working times so an exception is thrown when such a TimeRange is added to the WorkingHours. That is the correct behavior.
Well if you want all days to be considered non-working time then you could set the WorkDays to "None". If you want a day to be entirely working (when IsWorkDay resolves to true) then you would add a TimeRange whose start is "00:00" and whose end is "1.00:00".
Yes, without it, the control shows 9:00 AM - 5:00 PM background color as white, and gray for rest all. I just want to show either full gray or full white.
Is there any alternate way of achieving it?
Thanks!
The exception was added recently to fix a bug. A zero duration timerange is an invalid working time (i.e. you cannot have a working time without having some duration to the range) that would not have been treated as any working time. Is there a reason you were adding that?
I have already been using this on C# 4.0 application, which is already in production since past 1 year. It throws this error only on 4.5 and not on 4.0.