You need to add a x:ClassModifier=”internal” in the UserControl tag of the XAML file if you change the visibility of the class in the .cs file to internal. The file generated from the XAML file (e.g. MyControl.g.cs) needs to match the code-behind file (e.g. MyControl.cs). x:ClassModifier allows you to control the visibility of the part … Read more
There are a few ways to do this. Add your variable as a resource from codebehind: myWindow.Resources.Add(“myResourceKey”, myVariable); Then you can access it from XAML: <TextBlock Text=”{StaticResource myResourceKey}”/> If you have to add it after the XAML gets parsed, you can use a DynamicResource above instead of StaticResource. Make the variable a property of something … Read more
var item = eLevelData.ElementAt(index); If your collection is typed as IEnumerable instead of IEnumerable<T> you’ll need to use the Cast extension method before you can call ElementAt e.g. var item = eLevelData.Cast<RMSRequestProcessor.RMSMedia>().ElementAt(index)
I know it’s too late, but here is a better solution, without setting margins. Margins should be set differently for different heights of TextBlock or Checkbox. <CheckBox VerticalAlignment=”Center” VerticalContentAlignment=”Center”> <TextBlock Text=”Well aligned Checkbox” VerticalAlignment=”Center” /> </CheckBox> Update: It’s worth checking out @nmarler’s comment below.
ColinE is right with all his informations. I only want to add my subclass of ObservableCollection that I use for this specific case. public class SmartCollection<T> : ObservableCollection<T> { public SmartCollection() : base() { } public SmartCollection(IEnumerable<T> collection) : base(collection) { } public SmartCollection(List<T> list) : base(list) { } public void AddRange(IEnumerable<T> range) { foreach … Read more
I was getting the same error. The problem was that the link that Visual Studio was giving was for the 32 bit version, and I am running 64 bit. Some kind of error mentioning that when failing the install would have been nice… Here is the link for the 64-bit version of Silverlight 5 developer … Read more
You’re not limited to the dependency properties of the control you’re templating. In this case, while Button does not have a CornerRadius property, Border does, so you can use Border.CornerRadius instead: <Style TargetType=”Button” x:Key=”TabButton”> <Setter Property=”Background” Value=”White” /> <Setter Property=”TextBlock.TextAlignment” Value=”Center” /> <Setter Property=”Template”> <Setter.Value> <ControlTemplate TargetType=”Button”> <Border CornerRadius=”{TemplateBinding Border.CornerRadius}” Background=”White” BorderBrush=”#ccc” BorderThickness=”0,1,1,0″ > <ContentPresenter … Read more
An easing function is usually a function that describes the value of a property given a percentage of completeness. Different frameworks use slightly different variations, but the concept is easy to grasp once you get the idea, but it’s probably best to look a few examples. First lets look at the interface that all our … Read more
I would recommend Uri.EscapeDataString instead of using HttpUtility functions. See discussion in Server.UrlEncode vs. HttpUtility.UrlEncode.
I studied the Silverlight version of the Validation Error Template and created a WPF version of it which looks like this Added an animated GIF at the bottom of the post but after I finished it I noticed that it might be annoying because of the moving mouse in it. Let me know if I … Read more