Printable View
I love Response.Write with all my heart.
I always hear this....
"wahhhh, you should not use response.write, wahhhh"
Response.Write rocks man! You can make cool javascript and ajax pages without having to worry about learning any new technology.
Noone ever really says why you should not use Response.Write, they just repeat what other folks say. lol, kind of like Hollywood when it comes to politics. Right now, I'm reapeting something I heard in the movie..
Team America, World Police
Response.Write is a great debugging tool, but it's not good practice on a live site.
Response.Slap("ILMV")
That should be a new... thingy... thing... um... SHUT UP!! :mad:
You haven't provided a compelling reason to use it, either, you've just said it's cool, which is more or less an appeal to ignorance.
Using Response.Write is bad. Using Response.Write to write javascript is worse. Using Response.Write to write "cool" AJAX is shameful, something I'd never admit to in public.Quote:
Originally Posted by silentthread
The reason is, Response.Write occurs when the response stream is being sent and so the output can be sent at any point in the page rather than when it should be sent. If you create a script block of a function you've made, it's always best to use Page.RegisterClientScript (or its equivalent) so that the script is output to the correct place in the page. Incorrect placement of scripts (hence, Response.Write) can cause problems especially when you're working with the DOM. ASP.NET when used correctly effectively negates the purpose of Response.Write.
***puts on a grocery bag on head, and walks away in shame***
:ehh:
I was taught to use Response.Write for vbscript code. Thanks for that mendhak.Quote:
Originally Posted by mendhak
out.println
cnuplzsaymiwords.wrt