This question How do you deal with configuration files in source control? suggest to ignore them, and while it is an alternative I don't really want to have them moving the .ignore file all that much, seems like dirty to me.
Most of the team members have some sort of configuration in a number of versioned files which are not to be committed to the main branch. ie. app.config file with the local database etc.
How to deal with these files? They need them to have their environments running but at large they tend to forget to add new files to the repo because they start ignoring modified files.
I was thinking have some sort of script the removes them from the local file system when they compile so they can tell if the whole solution will stil compile or not when pushed into the repo, but I wonder is there is a better solution?