Statically-linked MFC has trouble loading string r

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

We have a statically-linked MFC application that uses CodeJock ToolkitPro. After upgrading from 18.3 to 18.6, I find that some of my applications don't load. In release builds, they crash. In debug builds, they pitch an exception because an untitled MFC doc/view document can't load the AFX_IDS_UNTITLED string resource.

I've debugged the issue pretty deeply, and I believe this problem to be caused by the upgrade to 18.6. Against this build, my application ends up with two string tables: one that's neutral, and one that's US/English. When building against 18.3, I have only one US/English string table. The desired  AFX_IDS_UNTITLED string resource is in the neutral string table, and MFC can't find it because it's looking for US/English strings (by design).

I see that the release notes include this item: "Inability to use some MFC resources in static configurations fixed for all localized modules"

Where can I read more about that issue? It sounds like it's directly related to the issue that I'm experiencing.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
mikeblas Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 29 June 2017 Status: Offline Points: 4	Post Options Post Reply Quote mikeblas Report Post Thanks(0) Quote Reply Topic: Statically-linked MFC has trouble loading string r Posted: 18 December 2018 at 7:11pm
	We have a statically-linked MFC application that uses CodeJock ToolkitPro. After upgrading from 18.3 to 18.6, I find that some of my applications don't load. In release builds, they crash. In debug builds, they pitch an exception because an untitled MFC doc/view document can't load the AFX_IDS_UNTITLED string resource. I've debugged the issue pretty deeply, and I believe this problem to be caused by the upgrade to 18.6. Against this build, my application ends up with two string tables: one that's neutral, and one that's US/English. When building against 18.3, I have only one US/English string table. The desired AFX_IDS_UNTITLED string resource is in the neutral string table, and MFC can't find it because it's looking for US/English strings (by design). I see that the release notes include this item: "Inability to use some MFC resources in static configurations fixed for all localized modules" Where can I read more about that issue? It sounds like it's directly related to the issue that I'm experiencing.

kinook Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 13 May 2003 Location: United States Status: Offline Points: 14	Post Options Post Reply Quote kinook Report Post Thanks(0) Quote Reply Posted: 14 November 2019 at 10:25pm
	I ran into this too -- after much spelunking, I found that this is resolved by removing the AFX includes from Common\res\Resource.rc Common\res\Resource-Neutral.rc Common\res\Resource_bg.rc
	Automate software builds with Visual Build Pro http://www.visualbuild.com