title: How to fix breakpoint expressions in Visual Studio 2017
body: <p>With VS2012 you could use some collection methods in breakpoint expressions such as this:</p>
  
  <pre><code>test.Contains("3")
  </code></pre>
  
  <p>However, with 2017 this throws the following error:</p>
  
  <blockquote>
    <p>The condition for a breakpoint failed to execute. The condition was
    'test.Contains("3")'. The error returned was 'error CS1061: 'string[]'
    does not contain a definition for 'Contains' and no accessible
    extension method 'Contains' accepting a first argument of type
    'string[]' could be found (are you missing a using directive or an
    assembly reference?)'. Click OK to stop at this breakpoint.</p>
  </blockquote>
  
  <p>Has this just something to do with my VS2017 instance or did they break something in 2017? Does anyone know how to resolve it. Breakpoint expressions were great in 2012 but they're pretty much useless in 2017.</p>