Resolve associated work items on check in.. Finally!

In Visual Studio 2015, Microsoft has fixed that default setting everyone hates.  Well, I bet the majority of developers hate it.  No? Just keep reading anyway.

By default, when you relate a work item to a check in, if the work item is not resolved or closed, it tries to resolve the work item for you.  Why?  I don't know. It's always been that way.


This, for me, is a real pain.  I don't, by default, want to do that.  I (usually) want to associate the work item.  So how do I change the default?  Prior to VS 2015 you had to edit your registry and restart Visual Studio.  Doesn't that sound like a great user experience?

Here is how to do that if you have not upgraded or need to use another version other than 2015: http://blogs.msdn.com/b/mitrik/archive/2010/12/03/how-to-make-associate-the-default-action-for-work-items.aspx  I think it still works.  I only have Visual Studio 2015 now so I don't care.

Thanks to user input the team at Microsoft has created a new setting. It only received 845 votes.  It should have received a lot more. https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3418758-in-the-team-explorer-change-default-state-value-o

The setting is under Tools > Options > Source Control > Visual Studio Team Foundation Server.



This isn't worded the best but that is the setting we have been asking for.  If you un-check the box, from then on the default will be associate for open work items.  You don't have to restart or anything but you will need to re-add your work item to see the affect.


Happy programming!

Comments

Post a Comment

Popular posts from this blog

Special Characters are Truly Special

Image
Do you remember the days before string interpolation in C#? I do. It was medieval. Those were truly the dark days of development. We would all use string formatting and concatenation and carried swords around to defend ourselves against giant beasts. Ok, maybe I'm the only one that was wearing a helmet but I'm kind of a weird guy. I think we can all agree that string concatenation is not all that fun. It might not be as dangerous as dragons, but it can still light your hair on fire when there is a bug in your code just to display some text. Classes in C# like StringBuilder helped make things safer but it wasn't all that readable. String.Format is easy but keeping the parameters in the right order isn't exactly a no brainer either. What if that code was just in a class behind a view? Can't we just put it in the view? In the code behind it was easily testable, but the context was lost, and it wasn't as simple as what we can do today. output = String.Format("
Read more

.NET Maui and VS Code

Image
  I was disappointed in the developer experience for .NET Maui and Visual Studio Code. I assumed that the popular debuggers and extensions would cover getting an app running. I am always up to date on my .NET and Visual Studio and Visual Studio Code so I just figured the tooling would be there. When the marketplace didn't really reveal a solution for me, I went searching. The best search result for me is the one that pointed me in the direction to get my .NET Maui CLI working.  That's right. I went to the CLI to get my IDE running the way I wanted it to. .NET MAUI with .NET CLI (Command Line Interface) Getting the .NET Maui workload and the maui-check command line tool installed really helped. Those installs made sure that the libraries and emulators were setup so I could run them without Visual Studio.  It also reminded me that I'll need some sort of emulator or device to connect VS Code to. dotnet new maui After running the CLI to create my solution and project, I realize
Read more

Where’s my phone update?

  http://www.microsoft.com/windowsphone/en-us/features/update-schedule-usa.aspx   I have a Samsung Focus.  If you look at the chart and details (as of today April 4th) I should get my February update 10 days to several weeks after AT&T gets thru testing.  AT&T isn’t done with testing at the time of this blog post.  So the February update should be called the June update and the March update could be called the July update.   I’m glad I don’t have a brick.  I’m glad I don’t have an Android 2.* and need to figure out if I can spend money on an app because it might actually not work on my version on the 2.x operating system.  I’m glad I don’t have an iPhone 4 with the bigger GBs and the cracked screens.   But how much different is copy and paste on the AT&T network than another network?  The Samsung update is in network testing right?  Or maybe that is just smoke and there is a bigger fire.  Tell me there is fire and I’ll not want the update. Otherwise quick puff
Read more