Re: ASP.NET Common Usage (Debate Please)
- From: Laurent Bugnion <galasoft-lb@xxxxxxxxxx>
- Date: Wed, 08 Nov 2006 06:38:45 -0600
Hi,
DaBrain wrote:
Many thank to anyone who has the time to read an reply to this.
Am a lone gun developer, I do not develop in team so this question
comes from a place where I just don't really KNOW what others are
doing, I just read, and what I read is ALL about Web Forms ONLY.
ASP.NET gives you a high level of comfort, by wiring the events, automating a lot of tasks, making the web react more like windows. However, I don't really agree with you when you say that postbacks are the Correct way. I think that POST has a lot of issues, for example when your end user refreshes the page and gets asked if he wants to resubmit. Also, don't forget that POST requests cannot be saved, when GET requests can get stored in a bookmark.
As you say, my strong opinion is that there is nothing wrong in doing GETs, and you really shouldn't get inhibited. The art of engineering is knowing when to choose which technology. On the web, we have POST and GET, and both have advantages and inconveniences. You have a huge advantage on new developers who only worked with .NET, and this is that you understand the depths of the HTTP protocol, because you come a long
way. Make sure to use this advantage when you work on a project.
Nothing wrong with a querystring :-)
Feeling better?
HTH
Laurent
PS: some will argue that the Correct way to go nowadays is to use AJAX ;-)
PS2: And guess what, it comes with GET and POST too
I have been developing web sites since 1995, then it was all PERL/CGI,
HTML on UNIX Now I am making the transition from ASP to ASP.NET. I am
developing in C# now.
My question is based around the concept of True "Web Forms"
Development, using Post Backs etc. As a developer I want to develop in
this manner because it is the Correct way to develop today. But in
some cases for example, in an online catalog, you want to use Query
string, Not only are catalog pages bookmarkable that way but the
navigation (back ,forward function)
The problem is this, as a responsible developer making a transition to
the new ways ... every time I develop something with a QueryString
(?printable=1 ... ?productid=54654) I feel as though I am breaking the
rules, reverting to old ways, not accepting the transition as it should
be. - I think. "what have I missed"
While I do use and enjoy true Web Forms development, custom controls,
and user controls...
...Is it also common to use GET requests in lots of your design? Should
I just think of ASP.NET web forms as a new and powerful "option"
available to me or should I think of it as the new must method of
design if you are going to use ASP.NET
Is it a case of:
Web forms are just a tool, use 'em when you can don't feel guilty
when you don't -- mix it up as you see fit you got the experience,
stop overthinking it! Nothing wrong with a querystring as long as your
code is good.
I think I need mentoring here, assurance, something like that. -
Strange that is.
Thank you very much for any replies
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch
.
- References:
- ASP.NET Common Usage (Debate Please)
- From: DaBrain
- ASP.NET Common Usage (Debate Please)
- Prev by Date: Re: What is <%$
- Next by Date: ASP.NET Shadow Copy With DLL Config File
- Previous by thread: ASP.NET Common Usage (Debate Please)
- Next by thread: Re: ASP.NET Common Usage (Debate Please)
- Index(es):
Relevant Pages
|
