one of those times Microsoft could go ahead and jump in and answer that
question for us. =)
I've developed a lot of web apps (good portion .NET now, mainly working with
SharePoint and DNN,Rainbow,IBS,Schwing) and the structure of ASP.NET is
pretty simple.
If you have ever studied MVC, you see where microsoft gets there ideas from
on it. Though its not a true MVC Architcture (though, it sorta is... you
don't really have to write the controller persay, the event wireup handles
that portion of it... which is nice, take that Java!) its still functions in
the fact you separate your presentation from your other logic. and ASP.NET
enforces this by
a) an ASCX file is nothing but html...
b) it just sets a Inherits in the page declaration above, this must inherit
from System.Web.UI.Control (pretty sure thats right), after that its all
gravy and property binding...
This is the point at which i see the similarities between Java's
Velocity/Struts/Swing/wahtever frameworks and a lot of the external
frameworks (DNN,Rainbow,IBS,etc) that exist...
So the only way I could see the limitation existing in VB.NET Standard would
be
a) the MDE/IDE doesn't support the ability to build web user controls
VISUALLY.
b) the compiler won't compile anything that inherits from .Control... which
would be the dumbest thing I've ever heard of. so like you herfried, I
would like to see if this is an actual limitation or a "placebo" if you
will.
=)
-CJ
"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:O$**************@TK2MSFTNGP12.phx.gbl...
* "CJ Taylor" <no****@blowgoats.com> scripsit: After all isn't a web control simply something that inherits from
System.Web.UI.Control? Which is part of the .NET framework?
I never wrote an ASP.NET web control... I don't know. I am interested
in the answer too...
--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>