<div style="margin: 12px 0px; font-family: arial; color: #333333; background: #ffffff; border: solid 4px #e5e5e5; width: 100%; clear: left;"><div class="CM_CTB_Content_Wrap" style="margin: 0px; padding: 0px;background-color: #ffffff;"><div style="border-bottom: solid 1px #dcdcdc; white-space: nowrap; margin-bottom: 8px; background-color: #eeeeee ;background-image: url(http://clipmarks.com/images/source-bg.gif); background-repeat: repeat-x; height: 24px; line-height: 24px; vertical-align: middle; padding-bottom: 4px; color: #666666; font-size: 10px;" ><a href="http://clipmarks.com/clip-to-blog/" title="see clips that are hot right now"><img src="http://content.clipmarks.com/blog_embed/21fd814a-3f9a-4bdc-8d49-10e82f010d9b/384991D2-8AA2-45CB-AA88-BB7A1637880A/" alt="" width="19" height="19" border="0" style="vertical-align: middle; margin: 0px 4px; display: inline; border: none; float:none;" /></a>clipped from <a title="http://www.codeproject.com/KB/aspnet/cuyahogafulltext.aspx" href="http://www.codeproject.com/KB/aspnet/cuyahogafulltext.aspx" style="font-size: 11px;">www.codeproject.com</a></div><blockquote style="text-align: left; padding: 0px 8px; margin: 4px 0px 8px 0px; background: transparent; border: none;" cite="http://www.codeproject.com/KB/aspnet/cuyahogafulltext.aspx"><SPAN class="ArticleTopTitle" id="ctl00_ArticleTopHeader_ArticleTitle">Extending Cuyahoga FullText Indexing (Lucene.NET)</SPAN></blockquote><div style="height: 2px; font-size: 2px; background: #dcdcdc; border-bottom: solid 1px #f5f5f5; margin: 2px 4px;"></div><blockquote style="text-align: left; padding: 0px 8px; margin: 4px 0px 8px 0px; background: transparent; border: none;" cite="http://www.codeproject.com/KB/aspnet/cuyahogafulltext.aspx"><P><A target="_blank" href="http://www.cuyahoga-project.org/">Cuyahoga</A> provides module developers with a simple to use wrapper classes for full text indexing with Lucene.NET. <BR />Although wrapper classes are easy to use these classes are not generic in nature. I mean <BR />we, as module developers, have to convert our custom content (be it static or dynamic) <BR />to a SearchContent object so that wrapper classes can index that content. Another similar limitation is when we perform search on the indexed content we can only get collection of SearchResult objects. I also want to mention that we, as module developers, have no control over which fields will be stored/unstored, which fields will be used as keywords or which fields will not be indexed while wrapper objects build the full text index. </P></blockquote></div><div style="margin: 0px 6px 6px 4px;"><table style="font-size: 11px;border-spacing: 0px;padding: 0px;" cellpadding="0" cellspacing="0" width="100%"><tr><td style="background:transparent;border-width:0px;padding:0px;">&nbsp;</td><td align="right" style="background:transparent;border-width:0px;padding:0px;width:107px" width="107"><a href="http://clipmarks.com/share/384991D2-8AA2-45CB-AA88-BB7A1637880A/blog/" title="blog or email this clip"><img src="http://content8.clipmarks.com/images/c2b-foot.png" border="0" alt="blog it" width="107" height="17" style="border-width:0px;padding:0px;margin:0px;" /></a></td></tr></table></div></div>

New from the makers of Clipmarks:  Amplify.com - Don't just share the news...Amplify it!