This thread is for discussions of Hosting Windows Forms Designers.

This article is simply great. I wish to see more like this one.
Arthur

what about a Web Forms designer?
Its possible to do something similar to your example using web forms designer?

Hi!

That article is really great.
It gave me the needed hints to step into this subject as deep as I wanted to. As i'm currently trying tom write a lightweight IDE for customumizing my own applications, i need to know, how the content auf the designer could be persisted and reloaded.
Is there any standard-mechanism for that, or will I have to implement my own handlers?

Any help would be appreciated!

Is it possible to use a treeview for that?

Good question ... I am actually tasked with building a Web Forms Designer.  I can load ASP.NET controls into my toolbox but of course can't drop those controls onto a Windows forms.  Can somebody help me!!  

Much appreciated -
Jon

Hello Tim,

 Thank you very much for this excellent article.  

 We have developed a graphical macro language in C# for our customers and one of the remaining hurdles that we have is the ability to edit the location of controls on a runtime form.  

 When the customer wants to edit our form, we scan our macro and generate controls on the form based upon the macro content.
 We would then like to display that form with the controls where the customer can position and size those controls like you can in this Designer example.  We would then iterate through the list of controls and remember their locations and sizes within the macro.

 Can you please lead us in the right direction?  We have been searching, trying, and reading many examples to no avail.  It appears that you possess this knowledge and could help us.  We are not inexperienced developers, I personally have been a software developer for 22 years in many languages.

  For example, how would you modify this example so that controls can be placed on the form with out the user clicking on the designer surface?

Thank you very much for your reply,
Rick Wirch

Hi!

That article is really great.  It gave me useful hints to start my application in perfectmanner , which looks like an .Net IDE . but can you please tell me how to remove a control from the designer form ....

Did you figure it out how to persist the designer content? I would appreciate any help on this
Thanks
Sgirase

Did you ever figure out how to remove controls from the form?  I need to do that same now

Tim:

Thanks for your nice article.

How can I get the location of a control in the design surface. I want to show the coordinates when the user moves the control, but I can't figure how!

Hi Tim, great article. I am currently creating a designer in a similar manner to your article, used to create pdf files. I am using it to add only textboxes and pictures, and can save the data to a database.  However I need to bring back the objects and add them to the form programmatically so the user can edit the objects (change the positions etc) Do you know how (or explain how) to add items to the designer surface programmatcally without using the drag and drop from the toolbox

Thanks

John Harry

hallo,
how to change Designer for design PocketPC components?

htx

v!tek

I have (am still) modifying this code to create a stand-alone Xaml generator for forms. The Xaml is structured for direct consumption by Windows Presentation Foundation. This was a great starting place.

In the course of my modifications and testing, I found a couple of bugs in the code which you may wish to correct in your source.

The Name property is listed twice in the property grid.

If you add a control (i.e. a Button), then change the name from the default (Button1) to anything else, then add another button, you get an unhandled exception. This does not occur if all like controls are added first then the names are modified. The cause is when the control is first added to the designer, it is added to the DesignerHost components collection using the default (Button1) control name as a key. When the Name property is updated, the components collection is not. When adding a second like control, the DesignerHost attempts to add it using the default name as well. However, since the first control was renamed, the default name of the second control is the same as it was for the first (Button1). An unhandled exception is thrown when the second control is added because the components collection already contains a control with the same key value.

I corrected this by attaching a handler to the PropertyValueChanged event of the PropertyGrid which removes the original entry for the control and readds it with the new name as the key whenever the Name property value is changed.