In my last post I explained reasons and gotchas to be concerned with when deciding to migrate from an Excel *.xla add-in to a C# add in. One of the reasons revolved around not having an easy way to use a source control product (we use Visual SourceSafe) to manage the actual code files of a VBAProject. This is because the *.xla is a binary file and using SourceSafe (and I would assume other products) you can not compare differences of a binary file (not to mention the VBAProject files that are part of the binary blob).
I mentioned that I automated getting the code files out of the VBAProject and into SourceSafe. I am sure there third party add-ins that allow a source control product to integrate into Excel, but the code is fairly simple to automate it yourself.... [More]