title: Is it an antipattern to use both traditional click events and ICommand?
body: <p>Generally, I think it's good practice to use ICommands to handle button clicks that need to do something (such as save user input). However, when the button does something strictly on the UI, like open a modal dialog, the view model doesn't need to handle that, or even be aware it happened. In such cases, it seems like it makes more sense to just use the button's Click event handler, but mixing and matching like that seems like a potential anti-pattern. Am I correct in thinking so?</p>
  
  <p>For example:</p>
  
  <pre><code>var openModalButton = new Button();
  openModalButton.Click += OnModalButtonClick;
  
  //Elsewhere in the view...
  var saveInputButton = new Button { Command = _vm.SaveInput };
  </code></pre>
  
  <p>It's not inherently clear by looking at the code why one uses a command, and why one uses a click event.</p>