I just checked your documentation about RadScheduleView and aspnet-ajax RadScheduler.
The first looks like this:
And for ajax it is:
As far as I can see the DB-Structure is different.
For Recurrence I found - for WPF
[RecurrencePattern] [varchar](100) NULL,
and for AJAX
[RecurrenceRule] nvarchar(1024) NULL,
[RecurrenceParentID] INT NULL,
My approach is to build a "schedule manager" in WPF - and an ASPX page on the intranet where everyone can view the schedules.
Does this work?
Or in other words - is there a compatible DB structure, or not?
Thanks in advance
5 Answers, 1 is accepted
Indeed the RecurrencePatterns for both the platforms are implemented differently, so I'm afraid you won't be able to use the two controls with the same DataBase. However what I can suggest you would be to implement the approach for WPF, for example, and use the ICal export/import functionality of the both controls in order to updated correctly the ASP RadScheduler. So would need to export the Appointments as demonstrated in this example (it is for Silverlight, but the approach is the same for WPF) and import them the ASP RadScheduler as demonstrated in this example. You can can test the approach using the examples I provided.
Hope this will help you to achieve the required.
since I have to handle a lot of appointments which change often import / export is not an option.
I place an appointment in WPF for tomorrow, immediately I have to export and import again via web.
five minutes later a coworker changes the times, export and import...
when an appointment is finished it has a result - change, export, import...
I really love your controls and especially the fact that most of them work very similar on different platforms.
of course there are differences but they are platform specific.
I can't understand that you decide to use an incompatible data model for the scheduler.
My hope was that you provide at least a "transformation layer" or such a thing...
The purpose of the examples is just to demonstrate a sample solution of how to implement binding to Database for both of the controls. What I can suggest you would be to use one of them as base project with its default implementation and modify the other project in order to be able to work with the same Database. However I also want to thank you for your feedback and to let you know that we will definitely consider creating such an integration "binding to Database" example for the two platforms at some point in the future. Meanwhile if you now decide to do it on your own, you could share it with the community through our Code Library section and you will be rewarded with Telerik points.
If you have any further questions let us know.
I just took a look at your source code (both WPF and ASPX).
Unfortunately in ASPX Appointment is a "mixture" of UI and Data.
An Appointment (for an example) there has a List of Appointment Controls as property.
In WPF it is a clean Data-Class following an interface.
But I see no simple way to share the data without reinventing the wheel.
Especially the Recurrence is implemented totally different.
I can try to add the WPF ScheduleView Assembly in my web project and use it's appointment (and related) classes for serialization.
But the ASPX appointment is very poor documented (missing info about RecurrenceState, RecurrenceRule, RecurrenceParentID, ...), so I have no idea how to come from a WPF-Appointment with Recurrence rule to a ASPX Appointment with RecurrenceState, RecurrenceRule and RecurrenceParentID.
I guess I have five possibilities:
a.) use Silverlight for the Web and WPF for the Desktop
b.) have no schedule view for the Web at all (only Desktop)
c.) Use only ASPX (no Desktop Client)
d.) Use (buy or build) something else to solve my problem
for a.) - not sure if this can run SL with my client (I'm not sure if they allow silverlight)
for b.) pretty bad since the "intranet dashboard" should inform about schedules
for c.) I guess this is also a problem since adding / changing appointments is security critical and intranet security is primarily implemented as "everything is read only"
for d.) also not the best idea - I use telerik especially to avoid "building my own for standard things"
By the way c.) (only ASPX) seems also not the best idea from the perspective of "external schedule access".
I mean that I will need a service (Windows Service) which uses the schedules (read, change).
Your WPF has a clear separation of Data / View (the control) - so I can use your Appointment classes in my service.
Also the classes are clearly documented an can be easily enhanced...
For the ASPX I'm not sure if / how this works.
First it is a "UI / Data" mixture in the classes and second I find no documentation about recurrence (how to change, how to handle "parents"...)
I'm just curious if I'm the only customer who has the need to share schedules over different platforms (Desktop, Mobile, Web,...).
Maybe you will implement such a "both on the same data" scenario.
If you do so, please consider, that the "WPF Data" is much better documented and the classes are easier to enhance (replace).
So if you do it - please do it with the "WPF Data Model".
Thanks for the feedback and for sharing your thoughts. The easiest way to go in this situation would be to use the WPF/Silverlight ScheduleView as you would be able to use the same example for the both platforms. However as there weren't many customer requests for such an integration example we haven't considered it yet. We will definitely keep in mind your recommendations once the example is considered for implementation.
If you have any further questions or concerns, please do not hesitate to contact us.