SolutionName.crunchsolution.local.xml is clearly a user specific file, the convention for User Specific Configuration Information additional to Visual Studio Solution and Visual Studio Project is that the file is ended with .user and not .local.xml
With that convention it is easy to exclude user specific configuration in the version control system (*.user). With "your" convention, it is not ;)
Best Regards
PS: If you have project specific user files, please follow the same convention.
This does make sense - although there is a hidden reason behind the .local convention :)
When originally designing the configuration system, I went into it with the intention that it could be possible to have 'shared' settings and 'local' settings. Each of these could be stored in separate files, so that the shared settings could be placed under source control and the local settings left on a VCS ignore list somewhere.
It hasn't happened yet ... and likely it won't any time soon. But when it does, I was trying to save everyone from needing to rename or lose all their configuration files :)
I guess this could always be done with a .user extension anyway ... perhaps .local.user. Though for projects I've worked on, I've found it useful to have the configuration files checked into VCS as other people on the team find them helpful. Likely this will depend entirely on the team/project you are working with.