Instructions on tabbars code compilation and debugging of vc6 function enhancement plug-in

First of all, if you only want to know the features and usage of "tabbars", please refer to the two articles: "Introduction to tabbars for vc6 function enhancement plug-ins" and "Instructions for installing and using tabbars for vc6 function enhancement plug-ins ".

1. How to obtain the source code of "tabbars"

(1) download from http://www.winmsg.com/cn/orbit.htm. if the website is abnormal, it cannot be updated to the latest version in time.
(2) download through this link (http://blog.csdn.net/images/blog_csdn_net/orbit/TabBars.zip)
(3) Leave your email and simple instructions in the comments in this article. I will check the comments regularly and send the "tabbars" Source code via email.
(4) thinking...

2. How to compile the source code of "tabbars"

The source code of "tabbars" uses the workspace of Visual C ++ 6.0 to organize the code. Therefore, to compile "tabbars", you must install vc6.0. Note that you must install the English version of VC, install the patch SP5. According to a friend, debugging in the Chinese version of VC is prone to problems. If SP5 is not installed with VC, the "tabbars" ID cannot be displayed in the plug-in configuration window, however, compilation and debugging are not affected.
Expand the released "tabbars" compressed package. The demo_cn directory is the Chinese version of the "tabbars" plug-in that has been compiled, and the demo_en directory is the English version of the compiled "tabbars" plug-in. The source code is in the source directory. The source directory contains two workspace files: "tabbars. DSW, and tabbarse. DSW "," tabbars. DSW is used to compile the Chinese version, "tabbarse. DSW "is used to compile the English version. The reason for organizing projects in such a simple way is that the use of isolated resources in VC plug-ins often leads to ide crash. The two work zones use the same set of code, but the resource files are different.
Open "tabbars. DSW or tabbarse. you can compile the "tabbars" plug-in for any one of the DSW. If your compiler settings are correct, you can compile the "tabbars" plug-in correctly and get tabbars In the DEBUG directory. DLL plug-in file.

3. How to debug the "tabbar" plug-in

The debugging of the VC plug-in is somewhat different from that of the common program. Because the plug-in is loaded into the VC process space, it is affected by the VC (msdev.. DLL. Only msdev is disabled. EXE to modify tabbars. DLL. The common method for plug-in debugging is to uninstall the "tabbars" plug-in first. The specific method is as follows:

Select "customize..." under the "tool" menu... "sub-menu command, select the" add-ins and macro files "tab in the pop-up customize window, and then add-ins and macro files: remove the "X" mark before the "tabbars" plug-in from the list.

When necessary, you can close all the windows (msdev. EXE) of the VC integrated development environment ). Start a VC integrated development environment (msdev. EXE), open the source code of "tabbars", and set "executable for debug session:" In the debug tag window of the Project setting window to the Startup Program of the VC integrated development environment, usually located:

... VC installation directory.../common/msdev98 // bin/msdev. exe

For example:

C:/program files/Microsoft Visual Studio/common/msdev98/bin/msdev. exe

As shown in:

Then start debugging. Another msdev will be opened in the VC integrated development environment. EXE process, switch to this msdev. EXE process. Use this process to load tabbars In the DEBUG directory. DLL plug-in file, the specific process is:

Select "customize..." under the "tool" menu... "sub-menu command, select the" add-ins and macro files "tab in the pop-up customize window, and then click" Browse... "button. In the pop-up file selection window, select the tabbars generated by the compilation. DLL. Click "OK" to load the debugging plug-in. A warning may appear in the middle. This should be in a different directory than the previously loaded "tabbars" plug-in with the same name, ignore it.

This msdev. the EXE process opens a VC project and then executes the "tabbars" function. when a breakpoint is set in the EXE process, the breakpoint should be valid.

After the debugging is completed, as long as the original msdev. EXE is not disabled, you do not need to perform the above settings to start the next debugging, because the VC has been recorded in the registry. If the original msdev. EXE process is disabled, You need to perform the preceding settings again during the next debugging, because the registry will be updated when the original msdev. EXE is disabled.

Note that you need to copy tabbars. ini to the directory where tabbars. dll is located when debugging tabbars. dll.