Version 1.0 of my project builds in Visual Studio 2008 successfully, But when I upgrade Visual Studio to version 2010, building my project failed (for some reasons).
My project changed and new release is ready (Version 2.0). It builds on Visual Studio 2010 successfully.
Now, if I want to access “my-project-version-1.0.exe”, I should checkout version 1.0, install Visual Studio 2008 and build it by Visual Studio 2008. I can’t build it by Visual Studio 2010.
I didn’t commit any output files of my project.
Should I commit output files (like *.exe, *.lib) when project in a stable revision to access older versions of my project in next times?
Is there any better idea?
Putting non-source files under version control is generally not a good idea. If you insist, you can add it in one commit, and remove it in the next one, and tag that commit.
What you can do however, is to keep the executables separately. For example if you use github, you can upload files so that you can download them later, for example already compiled executables or libraries.