Re: Ignoring the ASP.NET conventions...

I don't understand some of your terminology but here's some insight...

** We can control the output of the XHTML with declarations written into the
web.config file. The same can be done when using Visual Studio 2005.

** Iteration over objects and your other concerns just confused me as stated
but are generally understood as tasks performed with program logic using
your preferred language which common sense and contemporary trends suggests
should now be C#.

** ASP.NET Forms are in fact a single form.

** The head element and all of its contents can be created at will, edited
at will and managed at will using various classes in the framework.

What you need to do is what the rest of us have done: learn more about the
framework. Its humonguos and for awhile the big thing most of us related to
with one another was our mutual experience writing many lines of code when
in fact there was a class with methods in the frasmework mostly already
written for us. That's where you're at now. My best advice? Delve into the
documentation noting the latest ASP.NET documentation is at the subdomain
msdn2.microsoft.com.

Microsoft uses consistent terminology for their documentation and
knowledgebase documents. The word "overview" and other similar word are the
words you want to start with submitted to google or wherever used like
this...

// example 1
page lifecycle overview site:msdn2.microsoft.com

// example 2
htmlmeta class site:msdn2.microsoft.com

// example 3
3.0 site:msdn2.microsoft.com

Once you get the search results when we load one of the references such as
the page for the HtmlMeta class the menu which loads on the left of the page
must be consulted where you can find all other related links to the head
element for example.

You see, for the most part its about learning the correct terminology for
the .NET Framework and then using the documentation that will help you get
through this learning curve...

-
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/




"jufemaiz: jc" <euphemize@xxxxxxxxx> wrote in message
news:1182907216.055780.213810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is there any information out there on ignoring the desktop oriented
conventions of ASP.NET and developing web app's more in line with
traditional web app development. I need far more control over the x/
html output environment than ASP.NET is currently giving me (coming
from PHP + RoR background) - custom iteration over object groups,
inline controls within those iterators, linking *without* resorting to
client side javascript based form submission, "page as a single form"
desktop application method, mixing of html elements (form) to activate
server side alterations, altering information in the html > head
section of a page directly (there's got to be a way to do this).

Anyone, help?



.

Relevant Pages

  • Re: Continuations in Common Lisp (with apologies)
    ... >> Control effects, like side effects, should be documented. ... documentation is part of the software, ... in a language that also has full continuations. ...
    (comp.lang.lisp)
  • Re: Receiving single bytes with MSComm
    ... If you simply take as a premise that MSCOMM is the wrong ... > to locate any documentation in the MSDN. ... If it were an important control, ... > the lack of documentation clearly means this is an inappropriate control). ...
    (microsoft.public.vc.mfc)
  • Re: Basic Separator Line Control
    ... source code documentation. ... "RobinS" wrote: ... If you were the Microsoft employee that created a line control, ... My MSDN Subscription definitely makes me feel better about myself. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Receiving single bytes with MSComm
    ... I guess I've never before seen such convoluted code whose sole purpose is to receive a ... If you simply take as a premise that MSCOMM is the wrong approach, ... to locate any documentation in the MSDN. ... If it were an important control, ...
    (microsoft.public.vc.mfc)
  • Re: is tcl a reasonable alternative to unix shell scripts?
    ... Manpages are not the easiest place for a beginner to start. ... terminology is unfamiliar and there are few if any examples. ... Documentation), so you can browse them effectively. ...
    (comp.lang.tcl)