Home/ Questions/Q 3879690
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T22:45:20+00:00

When accessing a form or query string value from code-behind in ASP.NET, what are

  • 0

When accessing a form or query string value from code-behind in ASP.NET, what are the pros and cons of using, say:

// short way
string p = Request["param"];

instead of:

// long way
string p = Request.QueryString["param"]; // if it's in the query string or
string p = Request.Form["param"];        // for posted form values

I’ve thought about this many times, and come up with:

Short way:

  • Shorter (more readable, easier for newbies to remember, etc)

Long way:

  • No problems if there are a form value and query string value with same name (though that’s not usually an issue)
  • Someone reading the code later knows whether to look in URLs or form elements to find the source of the data (probably the most important point)

.

So what other advantages/disadvantages are there to each approach?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The long way is better because:

    • It makes it easier (when reading the code later) to find where the value is coming from (improving readability)

    • It’s marginally faster (though this usually isn’t significant, and only applies to first access)

    In ASP.NET (as well as the equivalent concept in PHP), I always use what you are calling the “long form.” I do so out of the principle that I want to know exactly from where my input values are coming, so that I am ensuring that they get to my application the way I expect. So, it’s for input validation and security that I prefer the longer way. Plus, as you suggest, I think the maintainability is worth a few extra keystrokes.

    • 0