I'm looking at converting a reasonably large web application - currently just short of 100 aspx pages, over to Silverlight. I've already done the most intensive pages, which has been great, but now looking at the overall framework and navigation side.
Now obviously the number of transitions and pages can be reduced quite a bit when going to a Silverlight experience when compared to the old web page design, but I've got a general question about which franework to choose.
In the past, the Telerik page navigation looked the obvious choice, but now that SL3 has the "Siverlight Navigation Application" project type, and I can see all the lovely demos ets on the web about how to use this with RIA services, can anyone offer any advice as to why I might stick to the Telerik framework for this part? Or am I likely to find the whole experience easier if I go with the standard project type for this?
I'm still intending to use Telerik controls on the most part by the way, just the navigation side I'm interested in.
Any comments and experiences anyone has on this subject, before I delve into the project, would ne most appreciated.
Thanks,
Tom
Now obviously the number of transitions and pages can be reduced quite a bit when going to a Silverlight experience when compared to the old web page design, but I've got a general question about which franework to choose.
In the past, the Telerik page navigation looked the obvious choice, but now that SL3 has the "Siverlight Navigation Application" project type, and I can see all the lovely demos ets on the web about how to use this with RIA services, can anyone offer any advice as to why I might stick to the Telerik framework for this part? Or am I likely to find the whole experience easier if I go with the standard project type for this?
I'm still intending to use Telerik controls on the most part by the way, just the navigation side I'm interested in.
Any comments and experiences anyone has on this subject, before I delve into the project, would ne most appreciated.
Thanks,
Tom