Oh, and as Bill pointed out, the true problem also is where to store all the necessary settings.

Charles Nurse We Need Your Help! I have thought alot about your documentation on creating new editor controls and have a question before I begin. Do you recommend having an image upload control in the profile property editor? The chart below shows your organization structure of the editor controls and need some advice on how to implement a new image upload control in the profile property editor.

Where in the organizational structure would you implement the image upload control in the profile property editor?

I did respond to you or someone else on the same topic in another thread.

There are two ways you can store the information.

1. If you decide to store the information as a url to the "image" then you should override the TextEditControl.  The Upload control would "save" the file in a location on your site - and the "location" would be stored as a URL in the profile.  The view mode would then display the url - using an <img> tag.
2. If you decide to add the file to the datastore using the DNN File/Folder API, then you could store the FileID in the proile - In this case as the FileID is an INteger you would inherit from IntegerEditControl.

I have actually built one that you could use - it is part of the "DotNetNuke Module Toolkit" that I have added to the DotNetNuke Forge on Codeplex - http://www.codeplex.com/dnnModuleToolkit.  In this toolkit you will find under "Controls" a FileControl (FileControl.cs) which is a generic File Control, and under Controls/EditControls are two controls - FileEditControl.cs and ImageEditControl.cs that wrap this control for use in the profile.