Why does R# say it can't resolve a referenced assembly in a building project, and then solve it (according to its own lights, anyway) in this way?

See more:

C#

Visual-Studio

In a project that builds, I ran ReSharper > Inspect > Code Issues in Solution

It gave me three of the same warnings:

"Cannot resolve assembly 'System.Drawing'"

The "code" (markup) causing the complaint was like so:

<metadata name="mnuMain.TrayLocation" type="System.Drawing.Point, System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
    <value>17, 17</value>
  </metadata>

R#'s suggestion was to "Convert attribute to nested element"

I took it up on its offer, and it changed the above to:

<metadata name="mnuMain.TrayLocation">
    <type>System.Drawing.Point, System.Drawing, Version=2.0.0.0, Culture=neutral, 
PublicKeyToken=b03f5f7f11d50a3a</type>
    <value>17, 17</value>
  </metadata>

When I re-run ReSharper > Inspect > Code Issues in Solution, the warning has gone away. Why? It still references the System.Drawing assembly.

It's true that the System.Drawing in my project's list of references is Version 3.5.0.0 (Runtime Version == v2.0.50727). Is that

why that R# gives that warning? But why does rearranging the xml appease it? Changing "Version=2.0.0.0" to "Version=3.5.0.0" just made matters worse. If I do that, the R# warning becomes an actual compile-time error of the same verbiage, namely, "Cannot resolve assembly 'System.Drawing'" but has no suggestions on how to fix it...???