Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy do I need to change "internalKeyToken" to "PublicKeyToken" in my resx file?
    primarykey
    data
    text
    <p>I have moved a C# solution file from VS 2005 to VS 2010, and on a new computer. One issue I encountered is that the original version of the resource file mixed <code>PublicKeyToken</code> and <code>internalKeyToken</code> like so: </p> <pre><code>&lt;data name="NAME" type="System.Resources.ResXFileRef, System.Windows.Forms"&gt; &lt;value&gt;PATH;System.Drawing.Bitmap, System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&lt;/value&gt; &lt;/data&gt; </code></pre> <p>and </p> <pre><code>&lt;data name="NAME" type="System.Resources.ResXFileRef, System.Windows.Forms"&gt; &lt;value&gt;PATH;System.Drawing.Bitmap, System.Drawing, Version=2.0.0.0, Culture=neutral, internalKeyToken=b03f5f7f11d50a3a&lt;/value&gt; &lt;/data&gt; </code></pre> <p>This file was generated by Visual Studio 2005 via use of the designer, though I'm editing it by hand to change instances of <code>internalKeyToken</code> to <code>PublicKeyToken</code>. Not doing so gives me a compiler error:</p> <pre><code>Error 19 Could not load file or assembly 'System.Drawing, Version=2.0.0.0, Culture=neutral' or one of its dependencies. The system cannot find the file specified. Line 225, position 5. </code></pre> <p>So, I am wondering:</p> <ol> <li>Why did Visual Studio 2005 somewhat arbitrarily switch between internalKeyToken and PublicKeyToken? The files are all in the same format.</li> <li>Why did that work before but now gives a "Could not load file" error? What has changed?</li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload