What is the difference in win32 debug and win32 release in visual c++?

In the build toolbar, there has 2 kind of build, debug and release. What are the difference? Can the program be run in computers which dont have visual c++ by using release?





Also, I saved a project in a computer and I moved it to another computer installed c++. Why it cannot be loaded?

What is the difference in win32 debug and win32 release in visual c++?
%26gt; there has 2 kind of build, debug and release. What are the difference?





Debug and release are the default two configurations projects start with. Debug is for debugging, where all the debug symbols are kept, there are no optimizations made, and so on. Release is the optimised, debug symbol stripped version.





If you don't understand when to use debug and when to use release, you aren't a level where they will make a difference for you. If you have just started learning C++, don't worry about it, and just use the debug version.





%26gt; Can the program be run in computers which dont have visual c++ by using release?





Yes, that's the idea. You can do the same for debug as well, but you don't distribute debug versions. You distribute the release versions. The debug versions are slow and enormous, and are only useful for debugging and testing purposes.





%26gt; Also, I saved a project in a computer and I moved it to another computer installed c++. Why it cannot be loaded?





I don't know. What problems do you run into? If you use VC++, and you saved and moved the project properly, all you have to do is open the project file or solution up in the other computer, using VC++.
Reply:Of course you know all these settings can be customized for each project, so it is not possible to give a complete answer.





But in general, debug includes debugging information, such as names of symbols and source code lines. Release has all this information removed, and also will perform extra optimization so the program will run faster and/or take up less space on disk. This might involve removing or reorganizing code, which would make debugging harder.





As for running on other machines without Visual C++, it depends if they have the required libraries. You can change your Release to do a static build, which will link all the needed library functions into the task image, and it should run on any machine. A dynamic linked image will be smaller (perhaps much smaller), but needs to have the proper libraries installed on the target machine before it can be run.
Reply:As for moving it to another computer, do you have the same versions of c++ on both? For example, VC6, VC7, VC7.1 (VS2003), VC8 (VS2005). The project files format changed for each and older ones won't open newer ones.