Sharing resources across projects
-
I have a number of MFC applications that use form views to enter data into a database. These all use static lib MFC. I have a number of forms that are needed in more than one application. What is the best way of sharing resources and their associated CFormView derived classes across projects. In the past I've used MFC Extension DLLs but keeping the resource id's in different ranges became a pain. Would one resource DLL for all the applications be a good idea (The apps are all part of one product)? Suggestions? Michael :-)
-
I have a number of MFC applications that use form views to enter data into a database. These all use static lib MFC. I have a number of forms that are needed in more than one application. What is the best way of sharing resources and their associated CFormView derived classes across projects. In the past I've used MFC Extension DLLs but keeping the resource id's in different ranges became a pain. Would one resource DLL for all the applications be a good idea (The apps are all part of one product)? Suggestions? Michael :-)
There's an additional option that (IMHO) simplifies things further. Why not have resources and its additional
CDlg-derived classes inside a regular MFC DLL and export a high-level C API along this line:/* Personal data dialog */
int PersonalDataDialog(PERSONA_DATA_STRUCT *pPersonalData);If you can follow this scheme, I'd say it is the most easily maintainable approach. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
-
I have a number of MFC applications that use form views to enter data into a database. These all use static lib MFC. I have a number of forms that are needed in more than one application. What is the best way of sharing resources and their associated CFormView derived classes across projects. In the past I've used MFC Extension DLLs but keeping the resource id's in different ranges became a pain. Would one resource DLL for all the applications be a good idea (The apps are all part of one product)? Suggestions? Michael :-)
Michael P Butler wrote: In the past I've used MFC Extension DLLs but keeping the resource id's in different ranges became a pain. There's a tool created by Andy Metcalfe called Resource Organizer. Michael P Butler wrote: Would one resource DLL for all the applications be a good idea (The apps are all part of one product)? This has the advantage when you plan to have multiple language versions of your product. Tomasz Sowinski -- http://www.shooltz.com
-
I have a number of MFC applications that use form views to enter data into a database. These all use static lib MFC. I have a number of forms that are needed in more than one application. What is the best way of sharing resources and their associated CFormView derived classes across projects. In the past I've used MFC Extension DLLs but keeping the resource id's in different ranges became a pain. Would one resource DLL for all the applications be a good idea (The apps are all part of one product)? Suggestions? Michael :-)
I do that when work with diferent languages. I put the resource into dlls, and share it from the dll.... Regards Carlos Antollini. Sonork ID 100.10529 cantollini