title: Using string-type resource identifiers in Windows .rc files / dlls
body: <p>We have a number of MFC extension dlls in our code base, many of which have embedded Windows resources defined in the projects .rc files (IDS_..., IDD_..., IDB_... etc). We use <strong>numerical identifiers</strong> to define our resources, taking special care that our resource ids don't clash across dlls, which requires some management to ensure our developers don't use the same numberings.</p>
  
  <p>I've realised that <strong>string-type resource identifiers</strong> might be an easy way to go, meaning that we can define unique identifiers for each resource in each different dll.</p>
  
  <p>My question is, are there any technical problems with doing this, for example:</p>
  
  <ul>
  <li>Will the MFC dll / resource chain still function correctly?</li>
  <li>Will the Visual Studio resource editor still work?</li>
  </ul>
  
  <p>I haven't found anything in the MS Technical Notes to say this would be a problem - I'd just wondering if people have had experience with this.</p>