On 7 October 2010 07:46, Leo Davidson <leonudeldavidson_at_gmail.com> wrote:
> > So I version the .suo file. Then, every time I compile, VS touches
> > and changes the .suo file
>
> Since VS re-creates the file every time the code is built, why does
> the file need to be versioned?
>
> If the file does need to be versioned (which IMO it does not), what
> use is there in storing an out-of-date version of it which is never
> updated the repository?
>
> I'm pretty sure you can just set a global ignore on *.suo and forget
> about those files. Note that they are created with the hidden
> attribute, too. The .suo files are essentially cache temp-files from
> what I can tell. Anything in them can be re-created from the source,
> and if they're out of date compared to the source then they are
> useless as well.
>
> (I fully agree that Microsoft should stop dumping crap like that in
> with the source code, but that's life with Visual Studio. :( )
>
Oh. Well you're right :D Thanks Leo! The global conditional compilation
symbols are defined in the .csproj file, but just happened to be mirrored in
the .suo file as well.
The strange thing is that for years I did exactly what you are suggesting -
ignoring the .suo file - but was having a lot of problems with other users
losing the global conditional compilation symbols when they checked out
their own working copies. So I reluctantly started versioning .suo, and the
problem went away.
Having said that, I've just tested it in a scratch repository with a test VS
solution, versioning the .csproj and ignoring the .suo, and it works fine.
So I can't explain the previous problems.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2668825
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-10-07 10:16:34 CEST