Fair question, James. A forum component for ASP.NET will not output HTML (<input type="text" id="Title" />). Rather, it will inject ASP.NET server controls (<asp:Textbox id="Title" runat="server" />).
The component developers are not forced to do this. They *could* output static and valid XHTML if they wanted. However, by injecting ASP.NET server controls rather than outputting HTML, such components leverage the power of ASP.NET. And the ASP.NET server controls *are* amazingly clever. The single downside of injecting server controls is that these controls do not output standards compliant XHTML. If anyone wants more information about ASP.NET, they are welcome to contact me. However, I don't want to skew this discussion away from the original question. Regards, Alister ----- Original Message ----- From: "James Ellis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 14, 2004 10:30 AM Subject: Re: [WSG] standards compliant .NET modules > Hi > Surely a .net developer can write their own function to output compliant > markup? seems strange that a language forces someone to use inbuilt modules. > > Cheers > James > > SomeNewKid wrote: > > >The ASP.NET framework does not produce standards compliant XHTML. Hence, no > >off-the-shelf forum component for ASP.NET will produce valid XHTML. > > > > > > > > > ***************************************************** > The discussion list for http://webstandardsgroup.org/ > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help > ***************************************************** > > ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
