Question

2

If you have been looking for a nice and clean way to parse your query string values, I have come up with this:

    /// <summary>
    /// Parses the query string and returns a valid value.
    /// </summary>
    /// <typeparam name="T"></typeparam>
    /// <param name="key">The query string key.</param>
    /// <param name="value">The value.</param>
    protected internal T ParseQueryStringValue<T>(string key, string value)
    {
        if (!string.IsNullOrEmpty(value))
        {
            //TODO: Map other common QueryString parameters type ...
            if (typeof(T) == typeof(string))
            {
                return (T)Convert.ChangeType(value, typeof(T));
            }
            if (typeof(T) == typeof(int))
            {
                int tempValue;
                if (!int.TryParse(value, out tempValue))
                {
                    throw new ApplicationException(string.Format("Invalid QueryString parameter {0}. The value " +
                                                              "'{1}' is not a valid {2} type.", key, value, "int"));
                }
                return (T)Convert.ChangeType(tempValue, typeof(T));
            }
            if (typeof(T) == typeof(DateTime))
            {
                DateTime tempValue;
                if (!DateTime.TryParse(value, out tempValue))
                {
                    throw new ApplicationException(string.Format("Invalid QueryString parameter {0}. The value " +
                                                         "'{1}' is not a valid {2} type.", key, value, "DateTime"));
                }
                return (T)Convert.ChangeType(tempValue, typeof(T));
            }
        }
        return default(T);
    }

I have always wanted to have something like that and finally got it right ... at least I think so ...

The code should be self explanatory ...

Any comments or suggestions to make it better are appreciated.

asked Feb 22 at 12:45

afgallo

community wiki

comments (1)

Jon Skeet · Answer 1 · 2/22/2009 12:51:58 PM UTC

Given that you only handle three different types, I would suggest three different methods instead - generic methods are best when they work well with every type argument which is permitted by the type constraints.

In addition, I would strongly recommend that for int and DateTime you specify the culture to use - it shouldn't really depend on the culture the server happens to be in. (If you have code to guess the culture of the user, you could use that instead.) Finally, I'd also suggest supporting a well-specified set of DateTime formats rather than just whatever TryParse supports by default. (I pretty much always use ParseExact/TryParseExact instead of Parse/TryParse.)

Note that the string version doesn't really need to do anything, given that value is already a string (although your current code converts "" to null, which may or may not be what you want).

JohannesH · Answer 2 · 2/22/2009 12:54:08 PM UTC

1

It seems to me that you are doing a lot of unecesary type convertions. The tempValue variables arere leady of the type you are trying to return. Likewise in the string case the value is already a string so just return it instead.

answered Feb 22 at 12:54

JohannesH

community wiki

add comment

AdamRalph · Answer 3 · 2/22/2009 1:02:04 PM UTC

In my application I've been using the following function:-

public static class WebUtil
{
    public static T GetValue<T>(string key, StateBag stateBag, T defaultValue)
    {
        object o = stateBag[key];

        return o == null ? defaultValue : (T)o;
    }
}

The required default is returned if the parameter has not been supplied, the type is inferred from defaultValue and casting exceptions are raised as necessary.

Usage is as follows:-

var foo = WebUtil.GetValue("foo", ViewState, default(int?));

C# ASP.NET QueryString parser

3 Answers:

Your Answer:

Not the answer you're looking for? Browse other questions tagged c# asp.net querystring or ask your own question.

Hello World!

Related