Good job. Glad you got it. It would be nice if VS and VisualSVN talked to each other a little better, and let you know somehow that you can't save changes. Probably too much to hope for given that Microsoft has a source control product of its own.

Sure, well worth three stars. Don't spend them all in one place ;-)

>SOLUTION !
>
>I use a great source control tool VisualSVN.
>
>Turns out ( god I love Google ) that with VisualSVN installed and a project open the tokens won't get saved. You have to open VS without opening a project, add the custom token to the list, then close VS. Next time you open up the token is there.
>
>Go figure.
>
>( VisualSVN worth checking out (little source control joke there). ) Free, extremely easy to install and at least for a single developer just trying to cover his tail look like a pretty good solution (certainly a better one than [b]no[/b] source control :) )
>
>Anyway, hope this saves somebody else a hassle (and encourages anyone who doesn't know about it to check out this task list token thing - really powerful. )
>
>( Oh, and notice I gave myself three stars. Why? Because I couldn't give 6 - I figure anybody can answer a question they know the answer to but answering one you *don't* know the answer to takes a special skill ;-)
>
>And I'm trying to win a toaster (there are prizes, right? )
>
>
>>>>Those are the best kind ;-)
>>>>
>>>>>Thanks for testing it. I thought that when I first started doing this it worked fine but now on this box for some reason it wasn't working. Maybe tomorrow it will go away ;-)
>>>
>>>Unfortunatley today it is still there. Only that box. Exports settings, close VS, import settings - token is there. Close VS, reopen - no token. All other setting stick - AAARGH
>>>
>>
>>Export settings? Import settings? Why do you need to do that? Your initials should remain in the token list under Tools, Options without you needing to do anything further. Are you able to change other settings and have them persist between one VS session and the next?