Dealing with VS2005 .suo files

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Klaus Hartke wrote:
>> Hi, I'm using Bazaar with a couple of Visual Studio 2005 projects.
>> There's a problem with the .suo file associated with the projects: it's always
>> modified, every time I open the project in VS, even if I don't modify the
>> source files.
>> This causes problems if I want to merge project versions, because I'm
>> forced to commit everytime.
>> I cannot remove it from versioning, because it has to be distributed together
>> with the project...
>> What's the best strategy in dealing with this type of files?
> 
> The following page on MSDN provides some guidance in this area:
> 
> http://msdn2.microsoft.com/en-US/library/ms171339.aspx
> 
> The relevant section is:
> 
> ----
> File Handling by Source Control
> 
> You can add the following files to Visual Studio source control:
> 
> * Solution files (*.sln).
> * Project files, for example, *.csproj, *.vbproj files.
> * Application configuration files, based on XML, used to control
> run-time behavior of a Visual Studio project.
> 
> Files that you cannot add to source control include the following:
> 
> * Solution user option files (*.suo).
> * Project user option files, for example, *.csproj.user, *.vbproj.user files.
> * Web information files, for example, *.csproj.webinfo,
> *.vbproj.webinfo, that control the virtual root location of a Web
> project.
> * Build output files, for example, *.dll and *.exe files.
> 
> 

So in summary, you shouldn't version the .suo files. As I understand it is just
the "workspace" information. Like what windows you have open, etc.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGqet/JdeBCYSNAAMRAv9uAKCadTZkhri6tEMsCFgeKw92cLukuACgizhj
9pdtJ1qr4BakHyec+ebyEIs=
=Seas
-----END PGP SIGNATURE-----