Thanks for the suggestion. I think i might have to do that if I cant get Xslt to work. My client wants me to modify the control as little as possble but if there is no way around it then i might have to create a custom control.
Its amasing how much one has to do just to get wild card searches possbile. We were going to use Ontolica search for that but it doesnt allow you to add BDC user profile properties in the free wildcard search version, or atleast i couldnt figure out how to do it. On Dec 12, 2007 3:03 PM, Sezai KOMUR <[EMAIL PROTECTED]> wrote: > Instead of inheriting from > Microsoft.SharePoint.Portal.WebControls.SearchResults > you can try to instead develop your own custom Search Results web part > from scratch, or even better code it as a custom server control and embed it > in the search results page. Although you would need to code all the > 'plumbing' if you do so, such as getting the search parameters, creating a > FullTextSqlQuery, executing the query, getting the results, implementing > paging etc. etc. > > > > It will involve a lot more custom code, but the advantage is that you will > have full control over the rendering implementation of the search results, > so you don't even have to use XSLT for the rendering if it's your own custom > webpart or control, you can choose to render the results however you like. > > > > I prefer to go completely custom, because I always find that I waste a lot > more time trying to get rendering perfect and its tough work, and you rarely > get it rendering 100% the way you would like. > > > > This is a good option if XSLT is not really your thing. > > > > > > If you love XSLT then Ishai's suggestion is better option for you, much > less custom development involved. > > > > Sezai Kömür* > **Senior Developer - BEng, BSc - Microsoft Certified Technology > Specialist - **http://www.moss2007.com.au/* > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf > Of *Ishai Sagi > *Sent:* Wednesday, 12 December 2007 12:48 PM > *To:* [email protected] > *Subject:* RE: [OzMOSS] Override Search Result Webpart > > > > I have some, but as I said, I am currently working on a blog post that > will simplify it – will let you know when I can (maybe tonight – I may have > time on the flight to do it) > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf > Of *Kanwartej Singh Basrai > *Sent:* Wednesday, 12 December 2007 2:44 PM > *To:* [email protected] > *Subject:* Re: [OzMOSS] Override Search Result Webpart > > > > Thanks mate I will look into that. Do you by any chance have any code > examples to get me started? > > > > cheers > > Tej > > On Dec 12, 2007 2:30 PM, Ishai Sagi <[EMAIL PROTECTED]> wrote: > > My advice would be to override the DataFormWebPart which gives you the > XSLT options, and then override SetDataSourceProperties and set a new > datasource to the webpart. > > I am planning a blog post about that, but it may take a while. > > > > *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf > Of *Kanwartej Singh Basrai > *Sent:* Wednesday, 12 December 2007 2:28 PM > *To:* [email protected] > *Subject:* [OzMOSS] Override Search Result Webpart > > > > Hi Guys > > > > Has anyone tried to override the search results webpart with a custom > one? I am trying to create a custom search results webpart that allows for > wild card searches. I managed to get the wildcard searches work by creating > a webpart which inherits from the Microsoft.SharePoint.Portal.WebControls > .SearchResults and overriding the oninit method, but I am having troubles > with rendering the control. Ideally i would like to create a custom property > that can take in an XSLT and transform the search results based on that like > the core search result webpart works, but any help in rendering the results > would be helpful. > > > > Cheers > > Tej > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.503 / Virus Database: 269.16.17/1179 - Release Date: > 9/12/2007 11:06 AM > > No virus found in this outgoing message. Checked by AVG Free Edition. > Version: 7.5.503 / Virus Database: 269.16.17/1179 - Release Date: > 9/12/2007 11:06 AM > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.503 / Virus Database: 269.16.17/1179 - Release Date: > 9/12/2007 11:06 AM > > No virus found in this outgoing message. Checked by AVG Free Edition. > Version: 7.5.503 / Virus Database: 269.16.17/1179 - Release Date: > 9/12/2007 11:06 AM > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
