61 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Ed Chavez commented  ·  May 7, 2013 5:24 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @kohler: Nope, that's not exactly correct. While you can get the menu thing working it doesn't really work as it used to identically. Even with the hoops described. Yes, it will work, sometimes - of particular note is how it has issues with InternalsVisibleTo....

• Kohler commented  ·  May 7, 2013 5:04 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It`s just hidden: http://serena-yeoh.blogspot.de/2013/02/visual-studio-2012-create-unit-test.html

• Carl commented  ·  May 1, 2013 2:18 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please, very unhappy

• Jared commented  ·  April 28, 2013 9:57 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  GIVE IT BACK!

• Ed Chavez commented  ·  April 22, 2013 5:10 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Bonehead move IMHO. Sure I've learned how to create unit tests from documentation and through a series of StackOverflow and Google searches was able to get the contextual menu working or rather, partially/buggy way. One thing that is inconsistent is the InternalsVisibleTo attribute. It works with the new model, but the contextual (right click + create unit test) doesn't - it no longer identifies/finds this setting - either in source (class) or assemblyinfo config file.

  So sure, I've gotten the "new" model working, *manually*. Yes, I know..."new" and "manual", awesome step forward...takes the cake for contradictory statements....

  Spent max votes (3) on this.

• Anonymous commented  ·  April 10, 2013 12:42 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is a great feature, would like to see it add back into VS2012.

• vencin chen commented  ·  April 3, 2013 5:48 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please add this feature back into VS2012.

• Jason Witty-Akhavan commented  ·  March 29, 2013 2:57 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please add this feature back into VS2012.

• Michael Freidgeim commented  ·  March 17, 2013 1:00 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Could you provide any links describing ALM ranger's project: Better Unit Testing with Test Code Generation?

• Dawa commented  ·  March 16, 2013 2:46 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Finally, a new project for Better Unit Testing! Hope to see this in the next update!

• Anonymous commented  ·  March 13, 2013 10:40 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Come on! Reenable this!

• Anonymous commented  ·  March 4, 2013 1:36 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Removing this great function was the was among the daftest things I've experienced from Microsoft.

• Anonymous commented  ·  February 26, 2013 9:00 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It was such a good feature, we need it back please!

• Aaron Havens commented  ·  February 25, 2013 6:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It would be nice to have this back in by default.

• Dawa commented  ·  February 11, 2013 12:40 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  You can get it back here.
  http://dl.my/2013/enable-create-unit-tests-on-visual-studio-2012/

• whoever commented  ·  February 9, 2013 4:37 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Sounds like it's just a matter of time before M$ push everyone over the cliff and heading for the Linux/Java/Eclipse world. If Steve hasn't kill Bill, Ballmer will surely finish the Jobs.

• Paul commented  ·  February 1, 2013 1:07 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is driving me crazy, and the keyboard shortcut workaround mentioned previously for some reason stopped working for me and I can't get it to work again. Please just put it back already.

• Brian Swiger commented  ·  January 28, 2013 11:24 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I wouldn't mind having this back in VS 2012. I thought about creating a Powershell script that would add this back based on the StackOverflow posting as a basis.

• Bas Hamer commented  ·  January 23, 2013 9:53 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  this apparently was my favorite feature as I spend most of my night trying to get it back. the work around refuses to work for me.
  Bringing back the functionality for public classes and methods would probably fix 90% of the grief.

  If you want to play nice then you can allow people to edit the T4 file that you use for generation to wire against an other framework.

• Mike Cooper commented  ·  January 23, 2013 8:17 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Any ETA Microsoft?