title: Default Constructor Parameter in MarkupExtension declaration
body: <p>Reducing this question to the bare minimum, consider this MarkupExtension class...</p>
  
  <pre><code>public class ProblemStatement : MarkupExtension
  {
      private readonly string _first;
      private readonly string _second;
      public ProblemStatement(string first, string second)
      {
          _first = first;
          _second = second;
      }
      public override object ProvideValue(IServiceProvider serviceProvider)
      {
          return this;
      }
      public override string ToString()
      {
          return _first + _second;
      }
  }
  </code></pre>
  
  <p>When this Xaml is declared...</p>
  
  <pre><code>&lt;Grid&gt;
      &lt;TextBlock Name="TextBlock1" Tag="{so:ProblemStatement 'hello', 'world'}"/&gt;
      &lt;TextBlock Text="{Binding ElementName=TextBlock1, Path=Tag}"/&gt;
  &lt;/Grid&gt;
  </code></pre>
  
  <p>...you see '<strong>helloworld</strong>' in the TextBlock as expected.  All's well to this point.</p>
  
  <p>But changing the constructor parameter to this...</p>
  
  <pre><code>public ProblemStatement(string first, string second = "nothing")
  </code></pre>
  
  <p>...and the relevant Xaml to this...</p>
  
  <pre><code>   &lt;Grid&gt;
          &lt;TextBlock Name="TextBlock1" Tag="{so:ProblemStatement 'hello'}"/&gt;
          &lt;TextBlock Text="{Binding ElementName=TextBlock1, Path=Tag}"/&gt;
      &lt;/Grid&gt;
  </code></pre>
  
  <p>the resulting error message is...</p>
  
  <pre><code>No constructor for type 'ProblemStatement' has 1 parameters.
  </code></pre>
  
  <p>There is a work-around, which is to chain the constructor by adding this statement to the class...</p>
  
  <pre><code>public ProblemStatement(string first) : this(first, "not provided") { }
  </code></pre>
  
  <p>and this will show '<strong>hellonot provided</strong>' in the TextBlock.  However, this also changes the semantics of the MarkupExtension and is not desirable in the larger, 'real-world' case.  Also the complexity of overloading increases dramatically when more complex types are used or the constructor arguments are of type 'dynamic'.  Also, for example, use of the new 'Caller Information' attributes is blocked altogether.</p>
  
  <p>So the question is: how to declare the Xaml so that the Xaml parser will honour a default constructor argument? </p>