How to index .xaml files for content
Hi,
How can I enable the xml filter or even the plain text filter for .xaml files ?
I have WDS beta installed. I want to set "file contents and properties" index setting for .xaml files. I tried to change the setting for .xaml files in the advanced settings area but my change does not persist. When I close the advanced settings dialog box the setting is not changed.
Hello Ahmed,
The 3.0 beta 2 should be indexing .xml files by default. If you do not have the beta 2, but instead have the beta preview I would suggest upgrading. Beta 2 is much more stable and has a UI to work with.
To change indexing properties with 3.0 beta 2 you should right click on the magnifying glass in the system tray and select Windows Desktop Search Options. Once there, click on Advanced and then on the File Types tab. You can then highlight the file type that you are interested in. At that point you can tell the indexer if it should index properties only or if it should index properties and contents.
If a file type you would like to index is not listed you can add it in the same location by typing the file extension in the box next to the Add new extension button and then clicking on the button.
Paul Nystrom - MSFT
Hi,
Thanks for your reply.
I do have the WDS beta 2 installed. And my question was about .xaml files not
.xml files. The xml files are being indexed fine. I did go to the Advanced Options section. You probably read my
question in a hurry. Let me copy it here.
"How can I enable the xml filter or even the plain text filter for .xaml
files ?
I have WDS beta installed. I want to set "file contents and
properties" index setting for .xaml files. I tried to change the setting
for .xaml files in the advanced settings area but my change does not persist.
When I close the advanced settings dialog box the setting is not changed."
-Ahmed
My apologies Ahmed. WDS will index .xaml files (properties and content) automatically when you add .xaml to the list of indexed file extensions and tell WDS that you want to index both the properties and content of those files. I just did this with WDS 3.0 b2 and was able to search the content of several .xaml files.
I think the problem that you are having isn't related to .xaml files, but to another issue we've seen where WDS 3.0 b2 isn't saving new file types when they are added in the WDS options. We currently have people looking into this issue. I'll post here when a fix/workaround is available.
Paul Nystrom - MSFT
Ahmed,
We are having trouble reproducing this problem at Microsoft. It would be great if you would be willing to answer the following questions. Having this information might help us better diagnose and solve the issue.
Paul Nystrom - MSFT
1. What is the exact process you are using to add the file type?
2. What Operating system are you running?
3. Did you have any versions of WDS running on your computer before you installed 3.0 beta2?
4. If you answered yes to number three, what version did you have and did you uninstall it before installing 3.0 beta 2?
5. Are you logged into your computer as an administrator?
1. I right click the wds sys tray icon and go to options and click advanced, go to file types tab, click on .xaml entry and for the "how this file should be indexed" option I choose "Index file properties and contents". In the entry for .xaml file it shows that the filter has been changed. I click on ok and then click on close for the search options dialog. However when I open the search options again the file types list shows that the filter for .xaml is not changed i.e. for some reason the change is not being persisted.
2. I am using Windows XP SP2.
3,4. I uninstalled wds beta 2 and now have installed the RTW version of wds 3.0. I think I had the wds 2.0 running before I installed wds 3.0 beta 2 but uninstalled it before installing wds 3.0 beta 2.
5. I am logged into my computer as an administrator.
Ahmed,
We haven't had any success reproducing this problem at Microsoft. Would you be willing to work with us to schedule a live meeting where we can look directly at your PC? If so, please contact me at a-paulny@microsoft.com. Hopefully we'll be able to find a solution to your problem.
Thanks for your continued feedback.
Paul Nystrom - MSFT