Hi everyone,

I know there has been a lot of discussion on this topic, and the general interest has been around improving the performance of Visual Studio. With VS11 Beta out, we have seen significant improvements in performance.

At this point, we do not have plans to re-write the IDE in native code, and we are going to close out this idea and release your votes for you to apply elsewhere.

We have the performance forum (link is on the bottom of the right hand side of the main VS UserVoice page) where you can vote for specific performance ideas, without using up your 10 votes on the main forum.

thanks,
Doug Turnure (MSFT) – Visual Studio PM

We love Resharper, but this UserVoice site is not really about this kind of thing. I’m going to close this out out as declined, and give everyone their votes back.

thanks,
Doug Turnure – Visual Studio PM

Thanks for the idea, and we’ve taken steps with RC to address the feedbck we’ve received to date. As it stands, I’m going to close this idea out – technically as declined, but we have made adjustments to the UI. While we did not adapt this particular suggestion, I hope you will find the changes are an improvement over Beta. If not, please feel free to make a new suggestion. Closing this item will give everyone back their votes, to apply against RC.

thanks,
Doug Turnure – Visual Studio PM

Thanks for the feedback. Though a bit controversial, this feature has been requested for a long time by many Visual Studio users and will therefore stay in Visual Studio 2015.

Mads Kristensen
Sr. Program Manager
Visual Studio Web Team

Thank you for your feedback. With the upcoming Visual Studio ‘15’ release, we are working hard to make Visual Studio more lightweight and easier to install. However, the system requirements of Visual Studio are incompatible with Windows RT, and we have no plans to port Visual Studio to that Windows edition.

Paul Chapman
Visual Studio Program Manager

Hi All

Thanks for voting on this UserVoice Topic. All ASP.NET related requests are now being handled at the ASP.NET UserVoice site, http://aspnet.uservoice.com/ – we are closing this request as declined to free up your votes here – please head over to the ASP.NET UserVoice and raise this topic there or vote for items that cover it.

Thanks!
Visual Studio Team

Dear supporters for this suggestion

Thank you for your feedback on this idea.

We designed the Code Lens indicator to be as close to the actual function declaration as possible, to allow you to make a better cognitive connection with it. At one point during the development of Code Lens, we actually tried locating it above the attributes as this suggestion requests. It looked great in simple cases, but unfortunately it started to feel “disconnected” from the declaration when more attributes were added. It really looked strange at around three attributes, but started feeling a bit odd around two.

Here’s a pathological “real world” case which illustrates this -

https://github.com/dotnet/roslyn/blob/master/src/VisualStudio/CSharp/Impl/CSharpPackage.cs#L26

Imagine the indicator above the attributes in this case.

For this reason, we’re declining this suggestion at present.

Thanks!
Mark Wilson-Thomas
Program Manager, Visual Studio Editor Team

Thank you for your feedback on this idea.

We have reviewed this and are not planning to complete this suggestion in the foreseeable future, as it has not gained sufficient user support relative to other suggestions in this area.

Mark Wilson-Thomas
Program Manager, Visual Studio Editor

Thank you for your feedback on this idea.

We’re glad you find Code Lens a useful feature, however at present we have no plans to bring it to the Community Edition of Visual Studio; it will remain one of the benefits of the Visual Studio 2015 Professional and Enterprise editions.

As such, we’re declining this suggestion at present.

Thanks!
Mark Wilson-Thomas
Program Manager, Visual Studio Editor Team

Thanks for the feedback. Page Inspector has been deprecated in Visual Studio 2015 and replaced by Browser Link which solves a lot of the same use cases.

Mads Kristensen
Program Manager
Visual Studio Web Team

Thank you for providing this feedback. Unfortunately we are not able to address this suggestion so we are releasing the UserVoice votes to use on other topic. Users with a paid subscription can optionally sign in to the IDE or obtain a product key to unlock Visual Studio. Eligible MSDN subscribers can obtain a product key from the “Subscriber Downloads” section of http://msdn.com or from your organization’s volume license administrator.

- Anthony Cangialosi
Visual Studio Program Manager

Thanks for all the feedback on this item. Please be advised that we have moved this item to the http://aspnet.uservoice.com
site and transferred the associated votes. We are going to close this item out and release your votes back to you so you can apply them elsewhere. Note that the votes will remain with the item on the other site, so the item will not lose any of its current vote count, and you will recoup your votes on this site. To track the status, post comments, or add votes on this item, please go to http://aspnet.uservoice.com/forums/41201-asp-net-mvc/suggestions/3090767-make-find-all-references-search-in-mvc-views and sign in using your current user ID and login.

I want to personally thank you for taking the time to share this suggestion. Since the suggestion you raised has not gathered many votes, the Visual Studio IDE team is prioritizing other suggestions and closing it at this time.

If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us!

Mark Wilson-Thomas
Program Manager, Visual Studio IDE Team

Hi feedback providers

We are not planning to revert to the old find dialog, nor allow disabling of the Quick Find feature in Visual Studio.

However we recognise that some of the issues raised in the comments do need to be addressed, for instance the usability/visibility of the switch toggles for case sensitivity. We’ll look at those as separate issues, however since we’re not planning to make the overall change that is suggested, I’m closing this item as declined.

Please continue to raise feedback on the usability and functionality of the quick find feature via the built-in feedback reporting system so that we can prioritize the work required (see https://msdn.microsoft.com/en-us/library/mt280277.aspx for details of the feedback tools).

Thanks
Mark Wilson-Thomas
Program Manager, Visual Studio Editor Team

I want to personally thank you for taking the time to share this suggestion. If you haven’t already, I’d encourage you to try out Visual Studio Code for this scenario.

Since the suggestion you raised has not gathered many votes, the Visual Studio team is prioritizing other suggestions and closing it at this time. If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us!

Paul Chapman
Program Manager, Visual Studio

Thank you for your feedback on this idea.

We have reviewed this and we do not plan to complete this suggestion in the foreseeable future since it has a relatively low level of support at this time, based on this item and other feedback channels.

Mark Wilson-Thomas
Program Manager, Visual Studio Editor Team

Hi Supporters of this suggestion

Since the suggestion has been around for some time and not gained a lot of votes, I’m marking it declined at this time.

Please do raise issues via the “Report a Problem” feature in Visual Studio 2015 and higher, if you are still seeing repeated IntelliSense failures; in your reports please do mention the language you are using at the time (C#, VB, C++, JavaScript, etc) , because Intellisense is delivered on a per-language basis so it is likely the problems are specific to a particular language. You can find “Report a Problem” in the top right bar of Visual Studio next to the Quick Launch search box.

Thanks for your feedback,

Regards
Mark Wilson-Thomas
Program Manager, Visual Studio Editor Team

I want to personally thank you for taking the time to share this suggestion. Since the suggestion you raised has not gathered many votes, the Visual Studio IDE team is prioritizing other suggestions and closing it at this time.

As you noted, there are a number of extensions available which address this need, some of which are free, so it may be that one of them will meet your needs

https://marketplace.visualstudio.com/search?term=t4&target=VS&sortBy=Relevance

If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us!

Mark Wilson-Thomas
Program Manager, Visual Studio IDE Team

Thank you for your feedback on this idea.

We have reviewed this and we do not plan to complete this suggestion in the foreseeable future since it has a relatively low level of support based on this and other feedback channels.

Mark Wilson-Thomas
Program Manager, Visual Studio Editor Team