Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I can't imagine why someone would go searching for tags inside HTML or XML files
I verified what you've done. It seems Windows 7 search can find the title name of xml documents but it can not search inside them as they can with standard text. It can though search inside html documents which is weird.Tried it on note.xml (Just another XML to add to all the others i regularly use). Nada.
XML file searches work fine for me. Check on this:
Yes, that is selected. However, can you search for items INSIDE the xml.XML file searches work fine for me. Check on this:
You have yet to explain what issue you are having. This person we're helping actually gave a specific example of what's not working.So I am not alone...I don't know if that's good or bad.
BTW, The Everything utility only searches the filenames, it doesn't help my case.
That's the legacy indexing service. If you had scrolled down, you would have seen Windows Search.Wanna know something truly ironic? I was going to suggest uninstalling the Indexing Service and then reinstalling it in "Add/Remove Programs - Turn Windows features on and off" and was going to do a step-by-step just in case when I noticed something quite odd.
That's the legacy indexing service. If you had scrolled down, you would have seen Windows Search.
Yes, that is selected. However, can you search for items INSIDE the xml.
For example, I created an xml file called test1234 then inside that put testabcd. When I search test1234 it finds the xml document, but when I type testabcd it does not find it. I tried the same test with HTML and it works for both searches.
Now you try.
Neither service depends on the other. They're two separate indexing platforms and shouldn't be used together. You shouldn't be using Indexing Service anymore as its obsolete - Windows Search replaces its functionality entirely.No, I knew that much, hence my post expressly discussing the Indexing Service which is directly tied to Windows Search
You have yet to explain what issue you are having. This person we're helping actually gave a specific example of what's not working.
We can't provide alternate utilities without knowing what shortcoming you're looking to address with them. You're being agitative, elusive, and not at all conducive to people trying to help you.Funny thing here is I dont recall asking for help with a specific issue. I asked for alternative utilities.
You have yet to provide anything of value to answer that question.
QFT. I was wondering if someone else had caught that...Neither service depends on the other. They're two separate indexing platforms and shouldn't be used together. You shouldn't be using Indexing Service anymore as its obsolete - Windows Search replaces its functionality entirely.
If you'd actually read the thread (you know, the one you created asking for help)... You would've seen one already suggested:You can't provide any alternative search utilities...or don't want to?
You have no reason to care about what shortcoming I am looking to address and you probably would not understand the details of it if I tried to educate you on it either.
Stop being a troll, answer the question asked or don't reply. It's pretty simple and requires very little effort on your part.
If you absolutely must "break" Windows 7 for whatever reasons (none really valid once it's properly indexed and configured, however), this is the only search tool that matters:
Everything
I gotta ask: who the hell searches for anything from the Command Prompt? My word...
I found some XML documents on my system and viewed contents, then searched and it worked as it should. It doesn't work when I create a new document. Maybe the Windows Search service indexes the name first, then over time contents.Tried this verbatim and it worked PERFECTLY, the contents are being searched. Hmmm....
<?xml version="1.0" encoding="ISO8859-1" ?>
<?xml version="1.0" encoding="ISO8859-1" ?>
<content>123456</content>
I just played around with this a little bit... Have you considered that the reason it's not working is that the xml file isn't actually an XML file, but a plain text file?
And by definition, a text file called test.xml is not an XML file - XML files have a proper form and syntax, that too could be an issue here because the extension says it's a given file type and when it goes to load it it's not matching the form and syntax of a proper XML file layout. That's akin to creating a test.html file with the 123456test content in it - you're sure as hell not going to load that in a browser because it's not a proper HTML file with the form and syntax a browser is expecting to find.