13 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...

• thenonhacker commented  ·  February 24, 2012 7:22 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  IN SHORT: Make us not rely on JetBrains ReSharper!

• Qwertie commented  ·  January 21, 2012 3:39 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Wow, 317 votes for an idea that is so nebulous. Personally I'd just like more refactorings available in VS Express (it offers only two). I write code at home, too, y'see. I'd use SD which has lots of refactorings, but it also has various misfeatures that annoy me really bad.

  How about an "extract common subexpression" feature which automatically identifies the common subexpressions and lets you pick one?

• AdminVisual Studio team (Product Team, Microsoft) commented  ·  November 3, 2011 12:36 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We agree that improved refactoring support would be a welcome productivity boost for Visual Studio! Though we only offer a handful of refactorings in Visual Studio 2010, we have partnered with DevExpress to offer a free refactoring tool, CodeRush Xpress, which greatly augments the set that is available for both C# and VB. You can download CodeRush Xpress at http://msdn.microsoft.com/en-us/vstudio/ee663901.

  Additionally, if you haven't seen it yet, check out the Microsoft "Roslyn" CTP at http://msdn.microsoft.com/roslyn. While this CTP doesn't represent a specific committment to more refactoring features coming from Microsoft in Visual Studio, it does reveal the public API that we are planning to make it easy for VS extension writers to create new refactorings and quick fixes. See the following "how to" documents to see just how easy it will be to create new features with Roslyn.

  How To: Write a Visual Basic Quick Fix: http://msdn.microsoft.com/en-us/hh543921
  How To: Write a C# Quick Fix: http://msdn.microsoft.com/en-us/hh543922

  Thanks,
  Dustin Campbell
  Visual Studio Program Manager

• igor commented  ·  August 29, 2011 10:39 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'm missing "introduce local" / "replace temp with query". This is probably the only field Eclipse beats VS.

• AndrewDover commented  ·  July 23, 2011 7:25 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I would love C++ refactoring.

• François REMY commented  ·  July 18, 2011 3:42 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Even C# refactoring tools are not sufficient for me. Please have a look at Refactor! Pro and implements some of the most useful things. Or make an agreement with them to provide a simplified (free) version of Refactor! like you did for VS2005.

• The configurator commented  ·  July 18, 2011 2:24 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This recommendation should have mentioned VB then...

• irperez commented  ·  July 15, 2011 6:40 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  If VB had the basic refactoring that C# has, all would be good. Thats what this recommendation is talking about. There is no extract as method in VB.

• Sławek commented  ·  July 14, 2011 2:10 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Improve code generation tool, based on convention:
  1. If I write IFoo Visual Studio should hint "Create interface for IFoo" instead of "Create class for IFoo".
  2. If I write this.foo = 123; Visual Studio should hint "Generate field stub for 'foo' in..." at first position instead of second.

• The configurator commented  ·  July 14, 2011 11:00 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  A lot of ReSharper users are woefully unaware of features built in to VS, like extract method, extract interface, reorder/remove parameters. Every single example given in this thread already exists in vanilla VS. Can you please post examples which _aren't_ already implemented, so they can be discussed?

• Scott commented  ·  July 14, 2011 9:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'd be happy with just "Extract as Method" and "Create interface from Class".

• ian.ringrose commented  ·  July 14, 2011 1:42 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I don't think Microsoft can keep up with ReSharper, so I seee no point in having only 99 reasons to buy ReSharper rathern then 101 reasons.

• kennethkryger commented  ·  July 14, 2011 12:47 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Microsoft should just buy ReSharper from JetBrains and include all the functionality into VS... Problem solved :)