Comments on common software of wood and wood-common tools for VC programmers

Http://blog.csdn.net/liquanhai/article/details/7215045

After the Chinese New Year, You can temporarily release things. It is necessary to sum up. I saw that the restaurant outside said "work is finished at the end of the year and the furnace is opened on the sixth day. Okay. I will continue to comment on the previous article.ProgramCommonly used tools. Of course, you have to ask your friends to leave a message to facilitate further sorting and supplement. Thank you! Happy New Year!The hyperlink address for each tool is provided in this Article. Please click to download:

1. Ide: I love VC ++ 6.0, but I also feel that visual studio2008 and 2010 are powerful and may have to go to the vs higher version sooner or later. Remember to install SP6 patch and msdn (msdn_1.5 _ simplified installation version) when installing VC ++ 6.0)

2. Assistance:

(1) Visual assist, like itCodeAutomatic completion, fast comment, switch the source file of the header file: vc_va_x_1561 (most suitable for vc6). With this tool, the input time can be saved.30% Or above.

(2) wndtabs:Used to display open source files and manage the source programs on the tab page., Required for VC 6.0.

3. program editor: notepad ++ and editplus. Ultraedit text editor, source insight, and codeblocks. I love notepad ++ and codeblocks. Code highlighting is pretty good.

4. Memory leakage check: boundschecker 6.5 and VLD. Tips: although they are very useful, it is best to disable them when they are not needed to prevent other problems.

5. Code formatting and export HTML: code2html and coolformat

6. Code Manager: the code snippet manager can be reused by Chen Deng,Codehelp, codelibray 

7. Version Control: tortoisesvn

8. Note: doxygen

9. Log: log4cpp

10. Packaging: Inno Setup, http://www.innoide.org/NSIs, setupfactory

11. dongle: Holy Dog

12. flowchart: viso 2007 and edraw

13. decompilation: idapro, ollydbg, and exescope

14. serial Port debugging: sscom32, A useful serial port debugging tool, I think this is the best practice. I 'd like to share with you .