SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I created a dummy webpart which inherits the CoreResultsWebpart. If I add the built-in SharePoint Search SSA to the default application proxy group, this webpart renders results just like the normal Core Results WebPart.

If I however set up SP2010 against FAST instead, and add the FAST Query SSA to the default proxy group, then nothing is displayed. The oob Core Result Webpart works of course.

Either there is some quirk to get this working, or there's a bug somewhere. I've tried it on two separate farms, with the same outcome.

share|improve this question
up vote 3 down vote accepted

We had a similar problem on extending CoreResultsWebpart, the problem was in .webpart file properties list, which lacked of some entries such as ScopeID, RelevanceView, etc.

We updated the list (copying properties from the original webpart), re-deployed, removed and reinserted webpart on sharepoint page, and all went ok.

share|improve this answer
I will double check all my properties and see if I missed anything. – Mikael Svenson Jan 29 '11 at 10:32

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.