[thelist] ASP.NET multiple forms question

[Chris at globet.com]

Tab

> I can't imagine any situation in which you'd need or even 
> want to have multiple forms on a .NET page.  Doing so would 
> lead to non-standard coding practices, which lead to reduced 
> marketability.

I think that the issue would be translation of a legitimate requirement
for multiple HTML forms on a page, to the .NET environment. For example:
one may require a search function and a login form on every page of a
website. On the "contact us" page, this would mean 3 forms in total. In
.NET this would typically mean having a search control and a login
control on each page of the website, and a "contact us" control on the
appropriate page. How ASP .NET implements these controls in the OSI
application layer is irrelevant for the majority of developers, it's
just a matter of realising that a "web form" does not translate to an
HTML form.

I haven't been using .NET for very long, so I would appreciate
correction if any of the above is incorrect.

-- 
Chris Marsh
Software Developer
t: +44 20 8246 4804 x828
f: +44 20 8246 4808
e: chris at globet.com
w: http://www.globet.com/

Any opinions expressed in this email are those of the individual and not
necessarily the Company. This message is intended for the use of the
individual or entity to which it is addressed and may contain
information that is confidential and privileged and exempt from
disclosure under applicable law. If the reader of this message is not
the intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please contact the
sender immediately and delete it from your system.