title: Using ModelBinder attribute vs. ModelBinders.Add()
body: <p>Can someone tell me the pros/concs to using <code>[ModelBinder()]</code> attribute vs. registering model binders via <code>ModelBinders.Add()</code> in global.asax?</p>
  
  <p>One advantage I can think of is that it's more explicit, whereas registering in the global <code>ModelBinders</code> is not as abvious to someone inspecting the action method.</p>
  
  <p>One tradeoff I can think of is that it's not reusable, since you would have to add this attribute to all action methods that need to use this model binder, whereas registering in the global <code>ModelBinders</code> will make it available for all action methods receiving that model.</p>
  
  <p>Is this the only difference?</p>
  
  <p>In other words, would stating this be correct:</p>
  
  <ul>
  <li>If you only use the model in one action method (maybe two, get + post), then use <code>[ModelBinder()]</code>.</li>
  <li>If you use the model in more than one action method, then register it in the global <code>ModelBinders</code>.</li>
  </ul>