Team explorer default resolve in VS2013

Question

I am getting annoyed by having to change Resolve to Associate in Team Explorer

Is there a way to set it to Associate by default?

Wantage

not as far as I'm aware, this has been there since 2012, many requests have been made to MS to alter this, there did used to be a registry hack to fix it but this was only for 2012. This guy seem to have a work around, but i have not tested or investigated this. deliveron.com/blog/post/… – Distrain

Why did your code not resolve the task? – Chapell

@MrHinsh cause one normally codes in small bits in TDD by passing a few tests and the moment they are done you want to push them to prevent possible conflicts but they do not resolve full task. – Wantage

I use Git locally for that. Then the only association is on a Push... – Chapell

And when one codes in small bits in TDD one does not CheckIn to the server untill one is ready to share code with a wider audience. :) I would only ever checkin to the server when a task is resolved. – Chapell

Answer 1

For visual studio 2013 this fixes the issue

[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\TeamFoundation\SourceControl\Behavior] "ResolveAsDefaultCheckinAction"="False"

Close

Answer 2

And now available in the settings UI in Visual Studio 2015: https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/3418758-in-the-team-explorer-change-default-state-value-o

Rusticus

Answer 3

Visual Studio 2019

I came here seeking an answer for VS 2019, as apparently the registry 'hack' no longer works.

There is now an setting in Tools -> Options for this, under Source Control -> Visual Studio Team Foundation Server called Resolve associated work items on check-in.

Un-check it to associate by default. Check to resolve by default.

Cod