Thanks Paul. Between you and Trent I actually figured this out!

Glad you got it.

To debug designer code you can go to the project properties of the project ,then debug and set the start action to stat external progam and point it to your visual studio instance devenv.exe.

Then debug will open a new instance of visual studio, you can then open up a test project and use the designer and debug will hit breakpoints etc in your designer code (type converters custom properties etc).

I hadn't set that, but I didn't need to in any case (it is a simple object, an IParentContainer), so the default is fine.



However, it did prompt me to work up a sample app that eventually allowed me figure it out. In translating the code from VB to C#, I didn't correctly handle this line:







The "Not Array.IndexOf(....) > -1" really was making my brain hurt in C# after adding all the parentheses to handle casting and I didn't do that right. I changed it to:







Now it works correctly. I'm still trying to figure out how to debug code that is written for the designer...



Thanks for the help!

Gregg,

Did you set the designerserialization attribute of the property?

I'm trying to get a component to set a ParentForm property at design time and have it serialized. I think you are doing something like this with the ParentContainer property when you implement the IInitOnFormLoad interface, but I'm not figuring it out.



First, is this entirely handled via that property? It appears to be setting the value of the property, when in design mode, but what calls the property in design mode to begin with?



Second, what causes the value to be serialized? In the setter, the component is added to the list of objects that need to be initialized. Is there something special that needs to happen to get it serialized? I'm using C# if that makes difference or requires some extra step.