When viewing the. RC resource file, I don’t know what’s going on. After turning it off and opening it in the resource view, this error will be reported.
I don’t remember moving anything in the. RC file. It just can’t be opened anyway
It is said on the Internet that if the cursor is positioned to the error and the XXX code is added, but if my cursor is positioned to the first line, this method is invalid
https://blog.csdn.net/liuyi1207164339/article/details/47131833
Solution: copy from the old. RC file, delete all the. RC file and replace it with the old. RC file. This should be a bug in vs2013.
Read More:
- Expected unqualified ID before string constant
- Expected unqualified ID before numeric constant
- RTR3InitEx failed with rc=-1912 (rc=-1912)
- [Solved] qt5.9 + vs2015 32bit Error: “-1: error: LNK1158: Can not Run “rc.exe”
- error C2057: expected constant expression (Can the size of an array in C language be defined when the program is running?)
- OpenGL environment configuration under VS2010 / vs2012 / vs2015
- [pit filling] problem summary of upgrading VS2010 project to vs2017
- Boot / etc/ rc.local What about invalidity? resolvent
- Callee RC: RegDB_ E_ CLASSNOTREG (0x80040154)
- Vant weapp uses the dialog pop-up box to prompt for path error
- Centos7 via / etc/ rc.local File configurator boot
- Spring cloud Alibaba 2020.0.rc1 does not integrate ribbon error reporting unknownhostexception
- Generate template asp.net Cs1010: newline in constant
- error: initializer element is not constant [How to Solve]
- Start Eclipse and pop up the “Failed to load the JNI shared library jvm.dll” dialog box
- error C2137: empty character constant
- Routing Error uninitialized constant TransController
- When vivado2017 is started, the “error when launching” dialog box will pop up vivado.bat : Launcher time out”
- After vs2019 is installed, the original vs2017 project cannot compile various error reports
- Vtk7. X is compiled and installed under vs2013 and vs2015