title: Can't inspect variables while debugging CLI project referencing .Net Standard Lib
body: <p>We are facing the same issue as this question asked on the visual studio community by Laurent: <a href="https://developercommunity.visualstudio.com/content/problem/376934/cant-inspect-variables-while-debuging-cli-project.html" rel="nofollow noreferrer">LINK</a>. </p>
  
  <p><strong>Problem:</strong> If we try to debug the C++/CLI project, all variables defined in .Net Standard library inspection fails with the message : </p>
  
  <blockquote>
    <p>Unable to resolve reference to type 'System::ValueType' in assembly
    'System.Runtime'.</p>
  </blockquote>
  
  <p>When the project is compiled below warning is displayed:</p>
  
  <blockquote>
    <p>warning C4691: 'System::Object': type referenced was expected in unreferenced assembly 'netstandard', type defined in current translation unit used instead</p>
  </blockquote>
  
  <p>And </p>
  
  <blockquote>
    <p>note: This diagnostic occurred while importing type 'App::Calc::Models::InputDataContext ' from assembly 'AppLib.Calc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a58edc04d4501d54'.</p>
  </blockquote>
  
  <p><strong>Steps to reproduce:</strong></p>
  
  <ol>
  <li>Create a .Net Standard (2.0.0) project containing a Struct/Class.</li>
  <li>Create a C++/CLI project using .Net Framework 4.6.1 (Same problem in 4.7.1) and include the previously created Struct/Class into a class.</li>
  <li>Run and try to add the variable to the Watch window.</li>
  </ol>
  
  <p>We have a large CLI layer and this going to be painful if we can't inspect the variables while debugging.</p>
  
  <p>So my question is it's been around six months since the question was asked and it hasn't been resolved yet. I want to know if anybody else has encountered the same problem and what is the workaround if any.</p>
  
  <p><strong>Update:</strong> Just received the following comment from the Visual Studio Feedback system.</p>
  
  <blockquote>
    <p>A fix for this issue has been internally implemented and is being
    prepared for release. We'll update you once it becomes available for
    download.</p>
  </blockquote>
  
  <p><strong>Solved:</strong> The issue is now solved by the Visual Studio Team.</p>
  
  <blockquote>
    <p>A fix for this issue has been released! Install the most recent
    release from <a href="https://visualstudio.microsoft.com/downloads/" rel="nofollow noreferrer">https://visualstudio.microsoft.com/downloads/</a>. Thank you
    for providing valuable feedback which has helped improve the product.</p>
  </blockquote>