On 6 October 2010 22:04, Andy Levy <andy.levy_at_gmail.com> wrote:
> On Wed, Oct 6, 2010 at 16:55, latortuga <latortuga_at_gmail.com> wrote:
> > I have a file that I change on a regular basis but never want
> > committed in the modified state. Would it be possible to get a feature
> > that auto selects in the commit dialog on a per file basis so that
> > specific files are always ignored or always selected?
>
> If you never want to commit the file, why is it versioned in the first
> place?
>
At the risk of derailing the OP's topic, I have a file like that. Visual
Studio stores its conditional compilation symbols for C# projects in the
.suo file. I have a lot of projects that require certain conditional
compilation symbols to work properly, so I consider the definitions to be
part of the project, not the individual users/working copy's environmental
settings. So I version the .suo file. Then, every time I compile, VS touches
and changes the .suo file, leaving me having to either revert or
unnecessarily commit it. FWIW I use standard integrated building (whatever
that's called), not nant or anything.
The real solution would be to convince Microsoft not to store those symbols
there, or have another place to define them that is more traditionally part
of the project. But it's been the way it is for about 10 years, so I doubt
anything is going to change to suit me.
Can anyone offer any more creative solutions? Is there a way in VS to define
these symbols in code somewhere and still have them apply globally? Sorry, I
realise this is halfway off topic.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2668674
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-10-06 23:24:38 CEST