.vb files are not content searchable (from the search textbox in start orb or from within Windows Explorer) due to a missing key in the Registry - by aljodAv

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 715487 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/25/2011 8:53:36 PM
Access Restriction Public


Files like VB, CPP, H, C, TLH, TLI and many others are name-searchable from the search textbox in start orb or from within Windows Explorer.
Except for VB files, all others are also content-searchable.
VB files are not content-searchable because there is a missing key setting in the Registry, pertaining to the VB files extension: in the Registry the setting for * PersistentHandler * is missing, making VB files are not content-searchable.

Suppose you want to find all files with the word CreateInstance. The Win7 and Win8DP search engines will find all files containing that word, except VB files, because they won't have their content indexed by the search engine, due to the missing key * PersistentHandler *.

This missing key should be set in the Registry by the VS11DP installation program.

I consider this report falls in the Usablity category, but it is inexistent. For this reason, I choose Performance in the combo box below.
Sign in to post a comment.
Posted by aljodAv on 1/18/2012 at 10:08 PM
If you found this topic useful, you may find also interesting the following suggestion, and vote for it:
Posted by Ralph Ursprung on 1/18/2012 at 2:04 PM
@Microsoft: Why did you fix it "in [...] Visual Studio"? those files should also be searchable by windows search if you haven't installed VS?!
Posted by Microsoft on 1/17/2012 at 11:29 AM
I am happy to report that we have fixed this issue in the latest internal build of Visual Studio. Please feel free to verify this on the next public release.
Posted by Aaron Lawrence on 1/10/2012 at 1:28 PM
Status now say fixed. When? Where?
Posted by aljodAv on 12/27/2011 at 7:40 AM
I want to make clear that when I mention *search engine*, I'm always referring to Win7's and win8DP's search engine, and not the one built in VS11DP.
Posted by MS-Moderator08 [Feedback Moderator] on 12/26/2011 at 11:02 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 12/25/2011 at 9:40 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)