designer

Problem: The Windows Forms designer does not work for an inherited user control when the base class is implementing an interface from another assembly. Platform: VS 2010 SP1, .NET 4.0 Framework Error: The designer could not be shown for this file because none of the classes within it can be designed. The designer inspected the following classes in the file: MyControl --- The base class 'MyBaseControlLib.MyBaseControl' could not be loaded. Ensure the assembly has been referenced and that all projects have been built. at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader

I am using the Configuration Section Designer for .NET to build a simple ConfigurationElementCollection . It appears that everything builds just fine and the code is automatically generated since the sub-elements are visible with Intellisense. Unfortunately, even though I have added elements to the collection in the configuration section, they do not exist at run-time; it shows the collection's Length property to be 0 - i.e. the collection is empty even though, as you can see in my example XML, I have clearly put them there: Example configuration <logParserSettings xmlns="LogParser">

When I want to edit/view the code for a winforms control/form i created, I need to right-click in the solution and select "view code". The default action for opening the file is "view designer". This appears to be the case for any C# file containing a class that inherits from a winforms control, even if this is indirectly. The daft thing is that VS does this if it can't run the designer (for instance when the control is not the first class in the file). Is there hint or attribute or workaround to stop VS from doing this? Right-click on a file in your solution Select "Open With..." Select

I have a UserControl with a public property using the following attributes: [Browsable(false)] [DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden)] I have tried deleting the owner form, re-creating a fresh form in Visual Studio 2010, and adding this UserControl to the form. It keeps adding a line like the following in the Designer file: this.vMyUserControl.MyProperty = ((MyNamespace.MyClass)(resources.GetObject("vMyUserControl.MyProperty"))); This crashes my application because this property is not designed to be created by serialization. Making the property read only at

I've started creating a Windows Store App for Windows 8.1 and now I encountered a problem concerning localization. I would like to display a string resource from a .resw file at design time, but every attempt to do so has failed, even though it works at runtime. When using the x:Uid attribute, I still have to supply the Text property (i.e. for a TextBlock) and I don't like to write the text twice. I also tried creating a property for the string on the viewmodel: public string Title { get { return ResourceLoader.GetForCurrentView("Strings").GetString("MainView_Title"); } } This is working at

Today at work, I stumbled upon a problem that was driving me nuts. Basically my goal is this: I have a UserControl1 , with a field of the type Collection<Class1> and a corresponding property Collection<Class1> Prop . Like this: public class UserControl1 : UserControl { private Collection<Class1> field = null; // later changed to: //private Collection<Class1> field = new Collection<Class1>(); [Category("Data")] [DefaultValue(null)] [Description("asdf")] public Collection<Class1> prop { get { return field; } set { field = value; } } } // later added: //[Serializable] public class Class1 {