I'm using VS.Net Enterprise Developer and
I have no System.Web.UI.Design namespace.

.I'm having awful problems getting my control  to be, well, professional. I cannot do anything at all with the designer  as I haven't got one ! I cannot even add attributes to the properties so that they show up in the correct categories when the control is right clicked - and that includes no description also. Every property I make just ends up in the misc category.Yet I have a downloaded samle project for Windows.Forms that manages to accomplish it (maybe it's just the asp  designer missing ?)

Mark .... anyone .... I don't know if you've done anything along these lines, if you have what are your namespaces for the designer ?

If not - don't worry I'll have another go, I might be doing something wrong.

It's odd that your Enterprise Developer hasn't got them either - maybe it's an Architect thang ... or at least another step up the software ladder and more dosh before they let you design  and potentially sell controls - i.e. make a living.

Wonder what the min software spec for an enabled designer is ?

Anyone know ?

When you add a reference to System.Design.DLL, the System.Web.UI.Design namespace doesn't show up ?? You have to manually add that ref. And it works for all above the Standard Edition, IIRC.

These are the namespaces required to do what you want
to do on my machine:

using System;
using System.ComponentModel;
using System.Web.UI;
using System.Web.UI.WebControls;

A bit weird but so what, thanx bud.

I know you know what I was thinking about whare and how namespaces are ordered and contained in the assemblies and I know you know I am chewing a hole in my bottom lip now.

Incidentally, are there any more obvious ones that I should now about, ummmmm .... lets call them misplaced namespaces shall we.

Thanx also for answering my questiones I posed to Vicky, I think she was getting a bit stroppy there, you may well have saved my buns there also.
And yes, you did get the job.

Another sticky wicket ,as I've just figured out, is that when you change stuff in your control  and add it to your toolbox what I have been doing (which takes ages) is to resert the toolbox and the re-add the modified control.

No Good.

So the reason I have not been seeing the changes I made was that it was using the older version  - despite showing the newer dll version number in the "CustomizeToolbox" dialog.

You simply need to close the solution and then reopen it .... refresh won't work  either.

Never mind - sorted now.

Can get on and pretty it all up a bit now.

(( And now another problem - I seem to have lost my margins from my Normal style in Outlook Express - oooohhhh .... does it never end ? ))

Alot of people seem to prefer having 2 instances of VS open when testing a control. I just use one and add the control  and a web  project to the same solution. That makes it impossible to test designer  code(I open 2 copies of VS at that point) but makes the control auto update whenever you make any changes. Very little re-starting, refreshing or messing with the ToolBar unless I've changed something to the ToolBar info it-self(icon, name, etc).

I have got all the properties and tagprefix working but not the designer.

I got the thing compiling and even running complete with designer  code .... but it won't give me the designer object at design  time. "Error Creating Control".

I decided to lump that because my control  was too complicated and simply made a bog standard  one as in
ms-help://MS.VSCC/MS.MSDNVS/cpguide/html/cpconhtmldesignersample.htm

And used their SimpleDesigner aswell.

Same thing - it compiles and runs with no errors and I can get it into the toolbox. But every time "Error Creating Control" when dragged from the toolbox.

Has anyone done this ?

I am a bit confused as the help says this ::
A Web Forms designer class controls the design-time appearance of a control by providing design-time HTML to a designer host. The .NET Framework provides a base designer class, System.Web.UI.ControlDesigner, that provides base functionality for a server control designer. ControlDesigner defines the following key methods for rendering design-time HTML.

which clearly states "System.Web.UI.ControlDesigner" but really means "System.Web.UI.Design.ControlDesigner"

So what sthe form on all this then guys ... does it work  or doesn't it ... is it me or isn't it ?

.I remember doing that sample. Remember having problems as well. Uhmm.....

Try changing the Designer attrib to: [Designer(typeof(CustomControls.Design.SimpleDesigner))]

[Designer("CustomControls.Design.MenuDesigner, CustomControls.Design")]

Is this correct ? i.e. namespace.designer, namespace

Thanx man, i'd never have found out how to do it, I was just baout to give up and stick with puuting border=1 in the tag and setting it to 0 in the code  !

hey, now I can do some good sh*te.

How did you find out about that, I've been digging in ms-help on attributes but there's so much of it !

I had a feeling it was that line, I don't know wht but
CustomControls.Design.MenuDesigner, CustomControls.Design

you know, it already has all the info it requires in CustomControls.Design.MenuDesigner .... why should it require the namespace again ?