When editing a rc file, then opening it in VC Dialog Wizard, I get error RC2104 because of TBS_NOTIFYBEFOREMOVE
I have a VC++/MFC dialog-based project.
In those dialogs, I'm using some sliders with "Notify Before Move" at true.
Sometimes, instead of using VS dialog wizard to edit them, I prefer to edit the related .rc file manually in a text editor.

The issue is, after editing the .rc file, when I'm trying to open a dialog in VS wizard again, I get this error:
"error RC2104: undefined keyword or key name: TBS_NOTIFYBEFOREMOVE"
I can still compile the project successfully, but I cannot open the project resources with VS wizard anymore.
The workaround is to remove manually the keyword, then I can re-open resources with the wizard, but I have to set every slider "Notify Before Move" setting at true again...

I don't understand why I get this error despite the project still compiling fine. If possible, I want to avoid the error and having to go through this workaround each time. Does anybody know how to avoid this error?
When editing a rc file, then opening it in VC Dialog Wizard, I get error RC2104 because of TBS_NOTIFYBEFOREMOVE
===

I have a VC++/MFC dialog-based project.
In those dialogs, I'm using some sliders with "Notify Before Move" at true.
Sometimes, instead of using VS dialog wizard to edit them, I prefer to edit the related .rc file manually in a text editor.

The issue is, after editing the .rc file, when I'm trying to open a dialog in VS wizard again, I get this error:
"error RC2104: undefined keyword or key name: TBS_NOTIFYBEFOREMOVE"
I can still compile the project successfully, but I cannot open the project resources with VS wizard anymore.
The workaround is to remove manually the keyword, then I can re-open resources with the wizard, but I have to set every slider "Notify Before Move" setting at true again...

I don't understand why I get this error despite the project still compiling fine. If possible, I want to avoid the error and having to go through this workaround each time. Does anybody know how to avoid this error?