Visual Studio 2012 - Strange behavior durring the commit

Based on TFS and local machine configuration, when we make a check-in we can set a task associate with the changeset to Resolve status. There are times when you cannot change a task status to Resolve, for example different policy on TFS machine. If you are using Visual Studio 2008 or Visual Studio 2010, everything will be away – an error message will be displayed that notified you that the commit ended without success.
When working with Visual Studio 2012 you will discover that even if an error is displayed during the check-in, the changeset will be pushed to the source control without having a task associate to it. You will receive the TF237124 error, but only after the commit is pushed to source control. This will happen even if on the TFS you enforce a rule that allow to commit only if a task is specified.
I hate this behavior, because a commit is made to source control even if an error appears.
To be able to assign a task to the changeset, you will need to open the task in TFS or in the browser, navigate to ALL LINKS tabs and link the changeset to the task (you will need to know the changeset number).
If you want to change the default behavior and not to mark the task as resolve in the TFS, you will need to set to the false value the following key:

// Visual Studio 2010
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation\SourceControl\Behavior]
"ResolveAsDefaultCheckinAction"="False"
//Visual Studio 2012
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\TeamFoundation\SourceControl\Behavior]
"ResolveAsDefaultCheckinAction"="False"

The problem with a check-in that is made even if an errors appears I expect to be solved in the near future. Is not acceptable this behavior.