designer

There's a famous bug in Visual Studio that prevents you from using the form designer on a subclass of an abstract form. This problem has already been elucidated and solved most elegantly by Urban Potato ; that's not the part I'm having trouble with. The trouble is, I have duplicated the technique described by Urban Potato, and included it in my project (which happens to be pretty big), and now every time I try to open the designer of my derived form, I get that Microsoft "frightfully sorry, old chap, but I'm going to have to kill you now" message (reminiscent of Otto in A Fish Called Wanda )

Often times while using QT designer I find myself needing to re-size things either by shrinking or expanding them. Whenever I try to do this the program does not allow me and simply reverts to the original default size it gives me when placing the object within my window, regardless of the layout I have. Why does it do this? And is it possible to change this so that I can re-size things to my own will without restrictions? I have been trying to learn how to properly use QT designer, but I can't find much information on this on the internet. Anything placed in a "Layout" will be automatically

For a WinForms control, I'd like to move certain settings into a sub object. One of them is a custom class containing all UI Strings, the other a OpenFileDialog: class MyControl: Control { // ... private OpenFileDialog m_dlgOpen = new OpenFileDialog(); public OpenFileDialog DialogOpen { get { return m_dlgOpen; } } } This adds the sub object to the designer, and allows to edit its properties (e.g. title, default extension, filter). However, the changes are nto added to the InitalizeComponent method, so they are lost. Is it possible to make this properties "persist" in the InitializeComponent

This question already has answers here : visual studio 2005 designer moves controls and resizes Form (10 answers) Closed 4 years ago . I am running visual studio 2008. Every so often when I go to the designer view of one of my forms, the designer will make the form slightly larger. This happens on forms where I have a minimum size. I want the form to be the minimum size so why does it keep adjusting the size on me? I was having this issue with a particular form that hosted a user control. Everytime I did a full Rebuild Solution it would make the form shorter. Found a simple solution: in the

I am having problems getting validation to work properly in the designer for my custom activity. The simplest sample to reproduce the behavior is as follows: I have a custom WF4 activity with a dynamic collection of arguments stored in a dictionary: [Designer(typeof(DictionaryActivityDesigner))] public class DictionaryActivity : NativeActivity { [Browsable(false)] public Dictionary<string, InArgument> Arguments { get; set; } public InArgument<string> StringArg { get; set; } public DictionaryActivity() { Arguments = new Dictionary<string, InArgument>(); } protected override void Execute

every time we open a *.xaml file in our project - we see not working designer and a lot of messages 'type not found' 'assembly not found' etc. After a couple of experiments, i found out a root of a problem : create new WPF application, create a folder in project root, add some value converter to folder, try to use it on your 'MainWindow.xaml' you will probably write something like this : xmlns:Folder="clr-namespace:WpfApp.Folder" and then <Window.Resources> <Folder:SomeValueConverter x:Key="someKey"/> </Window.Resources> You know... And, now the most interesting thing! when you build your