Telerik controls version 2010.1.422.1040
I recently took over a Silverlight Telerik scheduler which was having an issue with displaying appointments on a resource view. The only way I could get appointments to display is if “DisplayEmptyGroup” property on the scheduler was set to true. All the appointments were assigned to a resource, but would not display on the scheduler.
The issue was the assignment of the resources to appointments. The appointments were loaded and added to the Telerik appointment collection. Then each appointment in the collection was looped through and assigned to the resource. So as the appointments were added to the collection, they defaulted to an empty resource group since it was not yet assigned to the resource. For some reason, since the empty group is not displayed (“DisplayEmptyGroup” set to false), the appointments did not show up on the scheduler when the resource was eventually assigned to the appointment.
To fix the problem, I assigned the resource to an appointment before adding it to the collection. Problem solved!!!
Recently I upgraded our Silverlight 3 project with WCF services to Visual Studio 2010 Silverlight 4. Overall the upgrade went smoothly with a few glitches. Following are some basic steps:
- Install Blend 4 (if using blend references)
- Install Silverlight 4 toolkit
- Run the Visual Studio conversion wizard
- Update broken references
- Change all Silverlight projects to target Silverlight 4 in the project properties
- Delete all WCF references and re-add them
- When adding a service reference, choose “Reuse types in referenced assemblies" and select specific assemblies instead of the "Always generate message contracts" option.
If attached to source control, you may need to name newly added references differently or re-name existing references before deleting.
After running the solution through the conversion wizard I was getting several errors with the WCF services. I tried removing and re-adding the services several times with the “Always generate message contracts” option selected, which worked fine with Silverlight 3 in Visual Studio 2008. By selecting the option to reuse types and checking the specified assemblies, I was able to resolve my issue with WCF in Visual Studio 2010.