I have been working on this problem for most of today and found some interesting things: The main source of the problem seems to be relying on anchoring. If I use docking to position my controls, instead of anchoring, my problems seem to go away. I found a couple of blog posts from 2003(!), which … Read more
You should never modify .designer.cs. Period. Your changes will be overwritten without mercy. Update: To be a bit more helpful, C# since v3 (VS 2008) has included partial methods, which many designers will now use to let you implement custom behavior.
This allows you to use custom widgets defined elsewhere, which designer otherwise wouldn’t know about. For example, if you’ve defined a widget MyLabel derived from QLabel, then you can define it here and then just insert a QLabel as placeholder in your ui and promote it to MyLabel. The uic compiler will then include the … Read more
In the designer, click the control of interest. In the properties window (hit F4 to bring it up), there should be a little lightning bolt icon. Clicking the icon takes you to the list of available events for that control. Double-clicking the event name will wire up a stub handler and take you to the … Read more
I can repro your problem by creating a WPF application with a user control (put the user control on the wpf app, and build x64). Here’s my guess as to what’s going on: Visual Studio is a 32-bit application and the WPF designer has to load referenced assemblies (you see that behavior all of the … Read more
Using VS2010 you can use Design-Time attributes (works for both SL and WPF). I usually have a mock data-source anyway so it’s just a matter of: Adding the namespace declaration xmlns:d=”http://schemas.microsoft.com/expression/blend/2008″ Adding the mock data context to window/control resources <UserControl.Resources> <ViewModels:MockXViewModel x:Key=”DesignViewModel”/> </UserControl.Resources> Setting design-time data context <Grid d:DataContext=”{Binding Source={StaticResource DesignViewModel}}” … Works well enough.