This project is read-only.


Rate pages with 1 to 5 stars. Also you can give optional feedback.


Last edited Dec 29, 2007 at 10:35 PM by MikkoSalmi, version 3


MaoT Apr 19, 2010 at 2:21 PM 
sorry.. .net 3.5 cannot be selected to any app pool :(

MaoT Apr 19, 2010 at 2:20 PM 

I was so glad to get that rating webpart... but when i deployed the wsp i was not able to add the webpart to the page :( it gave me back an error:
Unable to add selected webpart(s).
Page rating: A web part or web form Control on this page cannot be diplayed or imported. The type could not be found or it is not registered as safe.

I checked, the webpart safe registration is in the webconfig file.

i chacked the application pool which has the .net Framework ersion v2.0 but the .Net3.5 with SP1 is installed. .Net framework cannot be selected for any application pool (Windows Server 2008 x64 with SP1)

any suggestions? :)

thanks in advance, Adam

KnoxCameron Apr 14, 2009 at 2:42 AM 
Thanks for the response!

I haven't tested with a large volume of data, so I haven't actually experienced any issue. Yes, as long as you configure your queries correctly (there is an MSDN article on the options available), your web part should be fine. However, there could be an issue if end users browse the list directly for some reason, maybe to get a report on all comments. You could probably go significantly higher than 2000 items before hitting an issue because you have simple metadata, but it still could become an issue at some point.

One approach could be to put the entries in the list in a folder structure based on the page being commented, so at least you would only include all the comments for a page in a single list view rather than all comments for a site.

One suggestion I would make (if you don't do it already) is to make sure that your list is flagged to be excluded from search, as we had an issue where we had a very large flat list and when the search engine hit it during a crawl it brought the whole system to a halt.

MikkoSalmi Apr 13, 2009 at 7:42 PM 
Thanks for commenting. I didn't actually know there are commenting option in these wiki pages so this is why the late reply. :).

The 2000 maximum item recommendation is only because the web ui in SharePoint doesn't work very well with more than 2000 items. We have succesfully deployed a solution with more than 18 000 rows in one list. We used custom web parts to get the data out of the list and we encountered no performance issues.

However, if you have some performance issues, please report them to Issue Tracker. Performance issues can be solved because they are most likely my fault (non optimized queries etc.).

KnoxCameron Jan 16, 2009 at 8:11 AM 
Works nicely!

I am a bit concerned though that it looks like all the page ratings for a whole site go into a single list. You could easily get more than the recommended 2000 maximum items in that list. Could that be an issue? Would it help if you indexed any of the columns in the list?