Contribute, suggest and share you experience here!

Aug 18, 2013 at 3:58 AM
SPCAF Contrib is out now. However, any contributions are highly appreciated!
We would like to hear you success stories as well as common pitfall or other neat stuff.

Any feedback is highly appreciated.
Aug 28, 2013 at 4:17 AM
Please add check for all cases described in this article:
Aug 30, 2013 at 3:11 PM
Hi! I think rule "SPListCollectionShouldNotBeFetched" should ignore fetching by guid, as it cannot affect performance. Actually, it is fastest way to get SPList and all methods like SPWeb.GetList are using SPListCollection[Guid] inside them.
Aug 31, 2013 at 8:51 AM
Hello guys,

Thanks for the feedback, appreciate your effort.

Could you please move the actual request to separate topics?
It would be much comfortable to to discuss and make up a solution.

Aug 31, 2013 at 9:03 AM

Most of the issues mentioned in the "Best Practices: Using Disposable Windows SharePoint Services Objects" article are already checked by SPDisposeCheck tool.
SPCAF has a neat integration and might run SPDisposeCheck, if SPDisposeCheck is installed in the system.

For SharePoint 2007/2010 we would recommend to go with SPCAF/SPDisposeCheck integration.
As for SP2013, SPCAF team is going to release custom dispose check which will be a part of SPCAF. This will be custom dispose checker due SPDisposeCheck doesn't support SP2013.

Let us now how is sounds to you and if there is anything else we might help you with.

Well, any call to SPWeb.Lists will fetch all the lists from the calling SPWeb.
It means SPWeb.Lists[title] or SPWeb.Lists[GUID] calls still fetch all the lists, iterates with list collection trying to find the target list with title/GUID matching.
It seems that SPWeb.GetList(listUrl) is still the optimal way to fetch the target list.

Also, could you please provide the actual code sample to make sure we get the case in the right way?