What to put under version control?

Question

Almost any IDE creates lots of files that have nothing to do with the application being developed, they are generated and mantained by the IDE so he knows how to build the a

Answer 1

This is where build automation and build files come in.

For example, you can still build the project (the two developers will need the same build software obviously) but they then could in turn use two different IDE's.

As for the 'junk' that gets generated, I tend to ignore most if it. I know this is meant to be language agnostic but consider Visual Studio. It generates user files (user settings etc..) this should not be under source control.

On the other hand, project files (used by the build process) most certainly should. I should add that if you are on a team and have all agreed on an IDE, then checking in IDE specific files is fine providing they are global and not user specific and/or not needed.

Those other questions do a good job of explaining what should and shouldn't be checked into source control so I wont repeat them.