Your search for Examine returned 5 results.
This is page 1 of 1
I've uploaded a zip file to our Umbraco that contains XSD
(Schema) files for the Umbraco Examine configuration files -
ExamineSettings.config and ExamineIndex.config you can
download the zip here.
Once installed and activated these files give you intellisense
and validation when editing Examine configuration
To install, place the .xsd files in the download in the
XML\Schemas sub folder of your visual studio install. Once
installed open your examine configuration files... and validation available on your Examine
Note: because the examine files are
included by web.config and form part of a larger configuration XML
document we can't give the root element a namespace and map the
My blog has been running Umbraco for 5 years and it needed a
little TLC. With origins in Umbraco 2.0.6 running on .NET 1.1 there
was a lot of clutter going on and templates with very strange names
So i've undertaken a little spring cleaning:
Upgraded to Umbraco 4.7
Set up auto tagging of posts using the awesome OpenCalais API
Rewritten search to use Umbraco Examine
Highlighted search results
Used Umbraco base AJAX to start suggesting results... examine to find similarly
Search result highlighting is based upon the
techniques described over on the wiki at our.umbraco.org and
I've also put together an
Umbraco package which allows you to get examine search result
a wiki page over at our umbraco that shows how to highlight
search terms in Umbraco
examine searches using
Lucene.Net.Highlight. Source code is attached to the wiki
The code was lifted from an
original forum post by Ismail so credit to him -
I wouldn't have known where to start otherwise. Also thanks to Shannon who made a quick
change in the latest version of examine to make the highlighting
easier and faster to do.
Once you get the code up and running the result is quite
pleasing - the highlighter will highlight terms even if you are
using fuzzy terms derived from your original search text:
I'd classify this is a 30 minute hack. I don't fully understand
the inner workings of what i've put
easily – using route hijacking.
What is missing?
In short, loads. By removing the Umbraco runtime from our front end site we lose.
A content cache
And lots more….
So for 90%+ of cases we’ll use Umbraco
cache and associated Examine indexes - and in scalable applications launching new instances fast is important.
Sometimes for really fast scalable apps that combine editorial structured content and user generated content Umbraco isn't the right