8
Vote

SP2010 Compatibility or Substitute

description

Is this tool SP2010 compatible? Will it work? If not, is there a method for making it work in SP2010? Are there plans for SP2010 compatibility? Is this sort of tool possible in SharePoint 2010? Is there a substitute for this in SPF2010? Information on this should be made clearer in the materials.

comments

FloridaRhino wrote Mar 2, 2011 at 8:26 PM

I agree!

wrote Jun 20, 2011 at 8:31 AM

AnneRobin wrote Jun 30, 2011 at 8:20 PM

I agree as well. This functionality is extremely popular with our site owners.

wrote Jun 30, 2011 at 8:21 PM

harrychen1 wrote Jun 30, 2011 at 11:10 PM

This is also one function we are looking for on 2010.

wrote Jul 8, 2011 at 3:01 PM

russgove wrote Jul 8, 2011 at 3:05 PM

I will definitely be looking to use this on my 2010 site. I installed it there and get ther error noted below. If I get some time i will trry to debug and see whats going on. BTW, whats the purtpose of the timer job in featureactived? why does it need to update the sitemap?


Error In OnPreRender: System.NullReferenceException: Object reference not set to an instance of an object. at TomShirley.WebParts.AccessChecker.SPUserAccessTreeNode.GetUserListPermissions(String login, SPList list, SPWeb web) at TomShirley.WebParts.AccessChecker.SPUserAccessTreeNode.DoesUserHaveListPermissions(String login, SPList list, SPWeb web, SPBasePermissions permissionMask) at

russgove wrote Jul 8, 2011 at 7:58 PM

I got it to work in Sharepoint 2010 by changinig one line of code. In SPPermissionsTreeNode.cs the code is calling a shareopoint internal method to get the users persmissoins. The signature of that method change etween 2007 and 2010. The second parameter used to be of type ISecurableObject, now its an SPSecurableObject.

If you change luine 242 of SPPermissionsTreeNode cs from

Type[] parameters = new Type[] { typeof(SPUserToken), typeof(ISecurableObject) };

to


Type[] parameters = new Type[] { typeof(SPUserToken), typeof(SPSecurableObject) };


It works. There is still some issue with the masterpage that i need to workout however (the display is all messed up).

Russell

russgove wrote Jul 8, 2011 at 8:37 PM

To fix up the display isues in 2010 just change the page tag on the two aspx pages in the LAYOUTS\AccessChecker folder to use v4.master :


<%@ Page language="C#" MasterPageFile="~/_layouts/v4.master" Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage,Microsoft.SharePoint,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %>and remove the SPWebPartManager from each of the aspx pages as well. With these changes, its working great in 2010!

AnneRobin wrote Jul 11, 2011 at 2:13 PM

Thank you for the display resolutions.

Does anyone have a resolution for claims (vs classic) based authentication? We receive the error when attempting to lookup a user: "The login name does not exist."

wrote Aug 11, 2011 at 5:51 PM

sbrickey wrote Feb 3, 2012 at 3:15 PM

Strategic Data Systems has ported this solution for SharePoint 2010, and posted it on their CodePlex project site (SDS SharePoint Library) at: http://sdssharepointlibrary.codeplex.com

sbrickey wrote Feb 3, 2012 at 3:20 PM

Strategic Data Systems has ported this solution for SharePoint 2010, and posted it on their CodePlex project site (SDS SharePoint Library) at: http://sdssharepointlibrary.codeplex.com

wrote Jul 4, 2012 at 1:53 PM

wrote Feb 14, 2013 at 7:25 PM