ASP.NET MVC DefaultValue attribute vs C# Optional Argument

Question

What is the difference between this ASP.NET MVC2 method signature, which uses the DefaultValue attribute:

public ActionResult DoStuff([DefaultValue(MyEnum.Alpha)] MyEnum enumToUse, bool printPage = false)
{
    //...
}

And this signature, which instead uses a C# 4.0 optional argument?

public ActionResult DoStuff(MyEnum enumToUse = MyEnum.Alpha, bool printPage = false)
{
    //...
}

Are the two statements different in any functional way, or is it just a matter of preference?

Darin Dimitrov · Accepted Answer · 2011-05-23 21:38:11Z

4

Same stuff, it's a matter of personal preference. I would use the second as it's less keystrokes. Also I think that the DefaultValueAttribute will involve some reflection voodoo so if you are anal about performance you might prefer the C# 4.0 optional arguments.

answered May 23, 2011 at 21:38

Darin Dimitrov

1.0m276 gold badges3.3k silver badges3k bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

ASP.NET MVC DefaultValue attribute vs C# Optional Argument

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related