[dotNetRDF-Develop] Issue CORE-317 has been added to a project you are monitoring.

[<tr...@do...>]

<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
  <tr>
    <td width="90px" valign="top"><b>Title:</b></td>
    <td>Upgrade VDS.Common to 1.2.0</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Milestone:</b></td>
    <td>1.0.0</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Core API</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Critical</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Improvement</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	We should upgrade to the latest VDS.Common since it resolves an issue occassionally seen by users where VS can report an unhandled NullReferenceException when there really isn&#39;t one. &nbsp;VDS.Common has resolved the issue by not auto-detecting whether null keys are supported but rather requiring the user to call a constructor that explicitly configures this behaviour.</p>
<p>
	&nbsp;</p>
<p>
	After upgrading the dependency version we will need to modify our constructor calls to set this where necessary.</p></td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=317" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=317</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
            If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
        </p>