Removing QAT resources from a MFC Dialog project?
up vote
0
down vote
favorite
I am been trying to resolve this issue for a while and may have stumbled over the solution. But I wanted to run it past you for confirmation if I may.
Background
I have a Dialog based application and I moved from VS2015 to VS2017 RC. My application supports several language translations using appTranslator. I noticed that the QAT (I think that is right, Quick Access Toolbar) resources suddenly appears in appTranslator. So they were now part of my application resources. Even though I am not using a QAC in my dialog application.
Resource Includes
I then stumbled over this in VS2017 RC in the resource editor:
I noticed this bit in there:
#define _AFX_NO_SPLITTER_RESOURCES
#define _AFX_NO_OLE_RESOURCES
#define _AFX_NO_TRACKER_RESOURCES
#define _AFX_NO_PROPERTY_RESOURCES
#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENG)
LANGUAGE 9, 1
#include "resMeetingScheduleAssistant.rc2" // non-Microsoft Visual C++ edited resources
#include "afxres.rc" // Standard components
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
#endif
I don't want to blindly make changes to my application, which is why I am asking first. But I saw the latter MFC ribbon and control bar resources and wondered if this was the culprit and / or if it can be removed?
mfc visual-studio-2017
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
add a comment |
up vote
0
down vote
favorite
I am been trying to resolve this issue for a while and may have stumbled over the solution. But I wanted to run it past you for confirmation if I may.
Background
I have a Dialog based application and I moved from VS2015 to VS2017 RC. My application supports several language translations using appTranslator. I noticed that the QAT (I think that is right, Quick Access Toolbar) resources suddenly appears in appTranslator. So they were now part of my application resources. Even though I am not using a QAC in my dialog application.
Resource Includes
I then stumbled over this in VS2017 RC in the resource editor:
I noticed this bit in there:
#define _AFX_NO_SPLITTER_RESOURCES
#define _AFX_NO_OLE_RESOURCES
#define _AFX_NO_TRACKER_RESOURCES
#define _AFX_NO_PROPERTY_RESOURCES
#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENG)
LANGUAGE 9, 1
#include "resMeetingScheduleAssistant.rc2" // non-Microsoft Visual C++ edited resources
#include "afxres.rc" // Standard components
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
#endif
I don't want to blindly make changes to my application, which is why I am asking first. But I saw the latter MFC ribbon and control bar resources and wondered if this was the culprit and / or if it can be removed?
mfc visual-studio-2017
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am been trying to resolve this issue for a while and may have stumbled over the solution. But I wanted to run it past you for confirmation if I may.
Background
I have a Dialog based application and I moved from VS2015 to VS2017 RC. My application supports several language translations using appTranslator. I noticed that the QAT (I think that is right, Quick Access Toolbar) resources suddenly appears in appTranslator. So they were now part of my application resources. Even though I am not using a QAC in my dialog application.
Resource Includes
I then stumbled over this in VS2017 RC in the resource editor:
I noticed this bit in there:
#define _AFX_NO_SPLITTER_RESOURCES
#define _AFX_NO_OLE_RESOURCES
#define _AFX_NO_TRACKER_RESOURCES
#define _AFX_NO_PROPERTY_RESOURCES
#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENG)
LANGUAGE 9, 1
#include "resMeetingScheduleAssistant.rc2" // non-Microsoft Visual C++ edited resources
#include "afxres.rc" // Standard components
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
#endif
I don't want to blindly make changes to my application, which is why I am asking first. But I saw the latter MFC ribbon and control bar resources and wondered if this was the culprit and / or if it can be removed?
mfc visual-studio-2017
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
I am been trying to resolve this issue for a while and may have stumbled over the solution. But I wanted to run it past you for confirmation if I may.
Background
I have a Dialog based application and I moved from VS2015 to VS2017 RC. My application supports several language translations using appTranslator. I noticed that the QAT (I think that is right, Quick Access Toolbar) resources suddenly appears in appTranslator. So they were now part of my application resources. Even though I am not using a QAC in my dialog application.
Resource Includes
I then stumbled over this in VS2017 RC in the resource editor:
I noticed this bit in there:
#define _AFX_NO_SPLITTER_RESOURCES
#define _AFX_NO_OLE_RESOURCES
#define _AFX_NO_TRACKER_RESOURCES
#define _AFX_NO_PROPERTY_RESOURCES
#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENG)
LANGUAGE 9, 1
#include "resMeetingScheduleAssistant.rc2" // non-Microsoft Visual C++ edited resources
#include "afxres.rc" // Standard components
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
#endif
I don't want to blindly make changes to my application, which is why I am asking first. But I saw the latter MFC ribbon and control bar resources and wondered if this was the culprit and / or if it can be removed?
mfc visual-studio-2017
mfc visual-studio-2017
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
asked Jan 9 '17 at 10:11
Andrew Truckle
5,38142146
5,38142146
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
That was the resolution. To remove or comment out:
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
I notice in the new Visual Studio Wizards that it refers to the Ribbon in the project setup, but you can't remove the setting as it is disabled.
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
That was the resolution. To remove or comment out:
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
I notice in the new Visual Studio Wizards that it refers to the Ribbon in the project setup, but you can't remove the setting as it is disabled.
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
add a comment |
up vote
0
down vote
accepted
That was the resolution. To remove or comment out:
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
I notice in the new Visual Studio Wizards that it refers to the Ribbon in the project setup, but you can't remove the setting as it is disabled.
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
That was the resolution. To remove or comment out:
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
I notice in the new Visual Studio Wizards that it refers to the Ribbon in the project setup, but you can't remove the setting as it is disabled.
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
That was the resolution. To remove or comment out:
#if !defined(_AFXDLL)
#include "afxribbon.rc" // MFC ribbon and control bar resources
#endif
I notice in the new Visual Studio Wizards that it refers to the Ribbon in the project setup, but you can't remove the setting as it is disabled.
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
answered Jan 9 '17 at 11:48
Andrew Truckle
5,38142146
5,38142146
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f41545541%2fremoving-qat-resources-from-a-mfc-dialog-project%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
