Well, I have not done this myself, but this is how I understand it: - you make a new project targetting a dll instead of an exe, and you add your images to that project just as you did so far for your exe project - in your existing exe project, you remove the images you currently have as resources; and you add code to decide which image dll is required (assuming you did build more than one image dll), you then load it dynamically, and then get the images from there. For dynamic dll load, and how to get at its content, please search "late binding" on CP. Come to think of it, there must be yet another alternative, based on internationalization; this is an official mechanism to support alternate sets of resources, normally intended to easily port your app to other languages/countries without changing the main code. I guess you could use it to just substitute alternate sets of images (and maybe some strings, such as company name). This too I have never done, and it also involves extra dlls, so it is very similar (if not identical) to what I described earlier. One possible difference is internationalization also supports a "default" country/language, which can be built-in (i.e. when no country-specific dlls are available or selected). More on this surely in the MS documentation. :) -- modified at 14:22 Monday 29th January, 2007
Luc Pattyn
