Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » .NET - Random T... » Visual Studio   (RSS)

Why doesn't my TypeConverter get called?

Consider the following code: public class MyControl : Control { [ TypeConverter ( typeof (SomePropertyConverter))] public Foo SomeProperty { get { ... } } } [ TypeConverter ( typeof (FooConverter))] public class Foo { ... } Now here are a couple of questions:

Do you really need a custom CodeDomSerializer?

When you author a new component for .NET for which you want to offer a smooth user experience within the Visual Studio designers, you may find you need to write a few more classes to get it working the way you want. For example, you may need to write

Brian explains Components, Containers and Services

Brian blogs about the fundamental concepts of the .Net component model. The post is typical of Brian - his explanation is always crystal clear!

How does the designer decide what properties to persist on a given component?

Any component has a bunch of properties on it. For example, the WinForms Button control has properties like BackColor, ForeColor, Text, Name, BackgroundImage and so on. When you place a Button on the Form in the VisualStudio designer and look at the generated
 
Page view tracker