I have a control with white text foreground color and transparent background color. Later on this usercontrol will be added into a different control that carries the real background color.
However during designing this, control due white foreground on white background in VS 2010, I can't obviously see anything. In there anyway to define a different color for just the design time?
I have tried this:
if (System.ComponentModel.DesignerProperties.IsInDesignTool)
{
LayoutRoot.Background = new SolidColorBrush(Colors.Blue);
}
But this doesn't work. Any tips?
UPDATE:
I dont understand how this works for you guys. I have created a new Silverlight 4.0 Application and have inserted this line of code into the ctor:
public MainPage()
{
InitializeComponent();
LayoutRoot.Background = new SolidColorBrush(Colors.Blue);
}
<UserControl x:Class="SilverlightApplication3.MainPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d"
d:DesignHeight="300" d:DesignWidth="400">
<Grid x:Name="LayoutRoot">
</Grid>
</UserControl>
When I go into Designer, I still dont see it as blue. And I dont even have any isInDesignTime Condition there. What I am missing here?
Thanks, Kave
Here's one way:
If you switch to creating a templated control, you'll need to wait to set things up in OnApplyTemplate, like in this example:
Assuming this is the template:
I also like to add conditional compile directives around code like this, as it's only for the developer/designer and is never needed at run-time.
Note that this entire technique works only when the
UserControl
you're creating is used within* another* UserControl/Control at design time. So, if the code I suggested above is placed in aUserControl
namedUserControlWithDesignMode
, then you must have anotherUserControl
,UserControlHost
, that contains an instance of theUserControlWithDesignMode
control to see the behavior work at design time. The code-behind for the currently edited control does not execute when you're editing it. It only executes when it's contained within another host (in Silverlight, anotherUserControl
for example).Alternate approach that doesn't involve code:
Cider -> ArtboardBackground
" color to a different color of your choice.Note: the "
Cider -> ArtboardBackground
" color theme field is found in VS2012 but I cannot confirm whether it has the same name in VS2010Good thread, especially when doing some MVVM the fact that UserControls appear on white when they are transparent is very annoying.
I'm sure you could do this in Blend with a state defined based on whether a designer is running, but I don't think that'd reduce the amount of work.
Still not sure how to avoid the code in the code behind and avoiding having to open blend, so if anybody has suggestions thanks in advance for posting.
That doesn't work, since it will make any child controls inside the usercontrol invisible at run time.
Did you try to set the Background on the UserControl? Not sure why but for me it doesn't work.
What does work is to set the Background of the Content, like so
then putting the following code in the constructor of the view
You can use following code within UserControl constructor:
For WPF:
For WPF / Silverlight:
One option would be to give the UserControl a background color, and then override that where you use it. So when you're editing the UserControl in isolation, it would have a background color; but when you're editing a control that contains that UserControl, you would see it with the transparent background like you want.
So the UserControl's XAML file would look like this:
And then in some other screen, where you use it, you could do:
Inelegant, but simple.
Another technique mentioned in this SO question is to use the undocumented property
d:DesignerProperties.DesignStyle
, which works great for applying a design-time-only style to a single control, but which doesn't appear to work for aStyle
in aResourceDictionary
that would apply to all of the appropriately-typed controls or elements under the scope of the dictionary.To solve this, on that same page I provide a simple solution for deploying a designer-only style into a
ResourceDictionary
. Here is a summary of that answer:First, put the desired style in a XAML dictionary in the normal way.
Then, in the C# code, remove the style from the
ResourceDictionary
when design mode is not detected. Do this is in theOnInitialized
override:Design Mode: Runtime Mode: