As you will note from the link : =
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/vbcon/=
html/vbconwebusercontrolsvscustomwebcontrols.asp
The design time abilities is one of the main difference between the two =
..
Web user controls are easy to make, but they can be less convenient to =
use in advanced scenarios. You develop Web user controls almost exactly =
the same way that you develop Web Forms pages. Like Web Forms, user =
controls can be created in the visual designer, they can be written with =
code separated from the HTML, and they can handle execution events. =
However, because Web user controls are compiled dynamically at run time =
they cannot be added to the Toolbox, and they are represented by a =
simple placeholder glyph when added to a page.
Web custom controls are compiled code, which makes them easier to use =
but more difficult to create; Web custom controls must be authored in =
code. Once you have created the control, however, you can add it to the =
Toolbox and display it in a visual designer with full Properties window =
support and all the other design-time features of ASP.NET server =
controls
[quoted text, click to view] "Wayne M J" <not@home.nor.bigpuddle.com> wrote in message =
news:OQqP4nUFEHA.2416@TK2MSFTNGP12.phx.gbl...
> I have seen plenty of documentation on Web Custom Controls and how to =
get
> them visible during the design stage of development, but I have not
> encountered anything as yet on setting Web User Controls such that =
they too
> are visible during the design stage.
>=20
> Is it possible?
>=20