The Add/Remove operation cannot be performed because the code element * * is read-only

In VS, when a large number of forms or controls are added, it is found that code cannot be generated automatically by the system IDE, such as automatically adding a button response function, and so on, when the RC Manager interface double-clicks the button to add a function, the prompt box "cannot perform an Add/remove operation because the code element * Began to think it might be the corresponding. cpp and. h were added read-only attributes, which were later found to be caused by the engineering NCB file.

Solution: Close vs, delete project corresponding. ncb file, reboot vs.

Problem reason: NCB is the abbreviation for no compile brower, which holds information for use in ClassView, WizardBar and Component Gallery (for ClassView, WizardBar please visit http:// msdn.microsoft.com/zh-cn/library/6761383e.aspx)

In the replication of resources or engineering, to modify the project NCB file, because to adapt to the new environment may cause NCB file confusion, and add a button response function is to modify the NCB file ClassView, WizardBar module data, data Chaos will cause automatic add function failure. Delete ncb file let vs re-establish NCB.

The function of several files with VS

The. clw file records the information for the class, and if a class in the ClassView is missing, regenerate the file

The. ncb file records the prompts for the class, and if the member function of the class and the hint of the variable are missing, regenerate the file;

The APS file records resource information and needs to make use of ready-made resources to modify 3 files,. rc files, Resource.h files and. aps files,. APS directly removed, enter the program, VC will automatically generate.

. APS: Intermediate files for binary resources, VC converts the current resource file into binary format and is stored in an APS file to speed up resource loading. Resource Assist File ... BMP: Bitmap resource file.

. BSC: A browse information file, generated by the Browse Information Maintenance tool (BSCMAKE) from the original browse information file (. SBR), which can be used to quickly locate in the Source Code editing window. For browsing project information, you must have this file if you use source brower. You can get rid of generate Browse Info File in Project options, which speeds up compilation progress.

. C: The source code file written in C language.

. A file generated by Clw:classwizard for storing class information. ClassWizard information file, INI file format.

. CNT: Used to define the structure of "Contents" in a Help file.

. CPP or. CXX: source code files written in C + + language.

. CUR: Cursor resource file.

. DEF: A module definition file for use when generating dynamic link libraries.

. DLG: A separate file that defines the dialog resource. This document is not necessary for VC projects, because VC generally put the dialog box resources in the. rc resource definition file.

. DSP:VC development environment generated engineering files, VC4 and previous versions use the Mak file to define the project. Project file, text format.

. The workspace file generated by the DSW:VC development environment is used to organize multiple projects into a workspace. Workspace file, similar to. dsp.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/net/

. Exp: The output file generated by the Lib tool from the Def file that contains the output information for functions and data items, and the link tool uses the exp file to create the dynamic link library. is generated only when the DLL is compiled, and some information in the DLL file is logged.

. H. HPP or. HXX: a header file written in C + + language, commonly used to define data types, declare variables, functions, structures, and classes.

. Hlp:windows help file.

. HM: In Help Engineering, this file defines the corresponding relationship between the ID value of the helper file and the dialog box, menu, or other resource.

. HPJ: A Help engineering file generated by the workshop, used to control the build process of the file.

. HPG, generate Help files for the project.

. ICO: Icon resource file.

. ILK: An intermediate file generated during a connection that is used only by the link tool.

. INI: Configuration file.

. LIB: A library file that the link tool uses to connect various input libraries to eventually generate an EXE file.

. LIC: User License Book file, which is required when using certain ActiveX controls.

. Mak: Make file, VC4 and previous versions of the engineering files used to specify how to build a project, VC6 the Mak file into a DSP file to deal with.

. MAP: A text file generated by the link tool that contains some information about a connected program, such as group information and public symbol information in a program. Executes the file's image information log file.

. MDP: Older version of the project file, equivalent to. dsp

. NCB:NCB is the abbreviation of "No Compile Browser", which contains information for ClassView, WizardBar and Component Gallery, which is automatically generated by VC development environment. No compile browse file. This file can be deleted when there is a problem with the auto completion feature. Generated automatically when the project is compiled.

. OBJ: The object file generated by the compiler or assembler, which is the binary intermediate file of the module.

. ODL: Source code files written in the object Description language, VC uses it to generate TLB files.

. OLB: A special dynamic link library with type library resources, also called Object library files.

. OPT:VC a file that is automatically generated by the development environment to hold various options in workspace. Project parameters file for the development environment. such as tool bar location information.

. PBI,. PbO and. PBT: Three kinds of files generated and used by profile of VC's performance analysis tool.

. PCH: Precompiled header files, larger, generated by the compiler when the project is established, which contains some of the code that has been compiled in the project, and will no longer recompile the code when the project is established in order to speed up the entire compilation process.

. PDB: A program database file that is automatically generated when a project is established, in which information about the program is stored and used to speed up the debugging process. Some data and debugging information about the program are recorded.

. PLG: Compile information file, compile error and warning information file.

. RC: Resource definition file.

. RC2: A resource definition file for use in special cases.

. REG: Registry information file.

. Res: binary resource file, which generates the res file after the Resource compiler compiles the resource definition file.

. Rtf:rich text Format (Rich text formatting) document that can be created by word or WordPad and is often used to generate help files.

. The SBR:VC compiler generates the original browse information file for each obj file, and the Browse Information Maintenance tool (BSCMAKE) uses the SBR file to generate the BSc file.

. Tlb:ole library files, where the data types, modules, and interface definitions of OLE Automation objects are stored, the Automation server is able to understand how to use automation objects through a TLB file.

. WAV: Sound resource file ...

Author: csdn blog Micro WX Smile