Submitting whole HTML document to Server

Is there a way to return the whole HTML document from the Client to
the Server "as is" so I can use ASP.NET to parse through it and look
for stuff?
I want to see what some client side JavaScript may have done to the
XHTML document."GMartin" <glenn.e.martin@.gmail.com> wrote in message
news:d9443226-88cf-4bb0-b1d6-4f9514c0ab02@.j20g2000hsi.googlegroups.com...
> Is there a way to return the whole HTML document from the Client to
> the Server "as is" so I can use ASP.NET to parse through it and look
> for stuff?
> I want to see what some client side JavaScript may have done to the
> XHTML document.
This doesn't directly answer your question, but it may be what you are
looking for.
http://projects.nikhilk.net/Projects/WebDevHelper.aspx
In addition to its many other features, it will show you the "live" HTML
source for a page (as modified by any javascript).
I'm looking to do it at runtime. Not with a utility while
programming.
On Feb 11, 1:31 pm, "Scott Roberts" <srobe...@.no.spam.here-webworks-
software.com> wrote:
> "GMartin" <glenn.e.mar...@.gmail.com> wrote in message
> news:d9443226-88cf-4bb0-b1d6-4f9514c0ab02@.j20g2000hsi.googlegroups.com...
>
>
> This doesn't directly answer your question, but it may be what you are
> looking for.
> http://projects.nikhilk.net/Projects/WebDevHelper.aspx
> In addition to its many other features, it will show you the "live" HTML
> source for a page (as modified by any javascript).

Suggestion

Hello,

I am working on a e-commerce application, which should
allows me to add three values each time I add the items to
the basket. Now I wonder where and how I should store
these values so that I can reuse them in the next screen?

Please advise me.Two options that come to mind are in a database, and in the Session
object. Which one you pick really depends on the requirements of your
application. For instance, if you want a user to be able to add three
items to the shopping cart and come back three days later, you'll need
a persistant data store like a database.

You might want to check out the source code to the Commerce Starter
Kit: http://asp.net/Default.aspx?tabindex=8&tabid=47 This is a
learning tool and will give you some implementation ideas.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 15 Dec 2004 16:42:07 -0800, "Vishal"
<anonymous@.discussions.microsoft.com> wrote:

>Hello,
> I am working on a e-commerce application, which should
>allows me to add three values each time I add the items to
>the basket. Now I wonder where and how I should store
>these values so that I can reuse them in the next screen?
>Please advise me.

Suggestion

Hello,
I am working on a e-commerce application, which should
allows me to add three values each time I add the items to
the basket. Now I wonder where and how I should store
these values so that I can reuse them in the next screen?
Please advise me.Two options that come to mind are in a database, and in the Session
object. Which one you pick really depends on the requirements of your
application. For instance, if you want a user to be able to add three
items to the shopping cart and come back three days later, you'll need
a persistant data store like a database.
You might want to check out the source code to the Commerce Starter
Kit: http://asp.net/Default.aspx?tabindex=8&tabid=47 This is a
learning tool and will give you some implementation ideas.
Scott
http://www.OdeToCode.com/blogs/scott/
On Wed, 15 Dec 2004 16:42:07 -0800, "Vishal"
<anonymous@.discussions.microsoft.com> wrote:

>Hello,
> I am working on a e-commerce application, which should
>allows me to add three values each time I add the items to
>the basket. Now I wonder where and how I should store
>these values so that I can reuse them in the next screen?
>Please advise me.