This is related to Q307351 at http://www.devexpress.com/Support/Center/p/Q307351.aspx
I am having the same problem (no standard images show up in the deployed application), but with a WinForms application deployed using the Windows Installer.
The problem seems to be that when a VB app is compiled in Release configuration, the Windows Installer does not detect DevExpress.ExpressApp.Images DLL as a dependency. This is true even if I explicitly include the DLL as a reference in one of the projects to try to force it to do so.
The workaround is to manually tell the installer to add the DLL to the application folder. This forces the copy of the DLL to the app folder on deployment and, once it is there, the system finds the images as normal.
The fact that this assembly is not detected by the setup programs is not our bug. If you reference this assembly and set its Copy Local property to True, you will see that it will be copied to the application directory.
Alternatively, you can simply explicitely include it into the setup program.
However, we see a room for improvements here. I have registered a corresponding suggestion in this regard: Modules - Convert the DevExpress.ExpressApp.Images class library to the standard XAF module and use it in project templates by default.
Thanks for creating the suggestion. I am already doing as you suggest to force the installer to include the DLL.
I agree with you that something should be done to force this to happen automatically. I really can't conceive of a likely use case where an XAF developer would not want the image DLL to be included in the distribution.
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.