title: Embedded Resource Name Loses Extension When File is Nested
body: <p>I have some scripts stored in files that I've marked as Embedded Resource. I nest each of these files under their associated <code>.cs</code> file. Unfortunately, for some reason, when you nest a file this way, the embedded resource name loses the file extension. This means that at runtime I have no way to identify which embedded resources are or aren't scripts. What can I do about this?</p>
  
  <p>One thing I tried that did not work: getting the <code>ManifestResourceInfo</code> object, which has a <code>FileName</code> property. Unfortunately this property is <code>null</code>.</p>
  
  <p>Another thing I tried was doubling up the extension. (like: <code>filename.ext.ext</code>). This didn't work, and everything after the first <code>.</code> is still missing.</p>
  
  <p>I tried naming the resource with something very different, and noticed that the resource name didn't even change. <s>It seems that it is generating the resource name for a nested embedded resource file based off of the "dependent upon" file</s>, which in this case is just a regular <code>.cs</code> file. I tried doubling the extension of the <code>.cs</code> file to <code>filename.extrastuff.cs</code> but the resource name still doesn't change. It insists on clipping everything after the first <code>.</code>.</p>
  
  <p>No, ok, I see now that it is actually naming the resource after the <em>type</em> defined in the <code>.cs</code> file, not the filename of either file. This is why the extension makes no difference. This means there is nothing I can do to either filename to help find the resource.</p>