LINQ to Active Directory

New Post: What about quering GC?

ggarbuglia — Thu, 14 Aug 2008 00:04:37 GMT

LinqToAD is a nice pice of code!
But what about searching the Global Catalog (a.k.a. cross domain search)?

Created Issue: LINQ query to both Users and Groups

johnpapa — Thu, 14 Aug 2008 00:03:18 GMT

I'd love to be able to write queries that hit both users and groups. Groups have a members property that is a string[] and Users have a Groups property tat is a string[], too. If these were a List<T> instead of a string[] we could cross query them much easier.

Nice tool overall, though. But that's my wish :)

Created Release: LINQ to Active Directory Refresh Release 1.0.1 (Jul 31, 2008)

Thu, 31 Jul 2008 21:15:24 GMT

Refresh Release 1.0.1

Includes bug fixes and support for:

byte[]- and GUID-valued directory attributes.
Bug fix for non-constant EndsWith, BeginsWith and Contains clauses.
Introduction of DirectoryContext with support for nested contexts and direct update support.
Extension methods for DirectorySearcher and DirectoryEntry classes to create queryable objects on the fly.
Support for DirectorySearcher in data source and context constructors enabling more flexibility for search options.
Updated samples to use the new available features.

Released: LINQ to Active Directory Refresh Release 1.0.1 (Jul 31, 2008)

Thu, 31 Jul 2008 21:15:24 GMT

Refresh Release 1.0.1

Includes bug fixes and support for:

byte[]- and GUID-valued directory attributes.
Bug fix for non-constant EndsWith, BeginsWith and Contains clauses.
Introduction of DirectoryContext with support for nested contexts and direct update support.
Extension methods for DirectorySearcher and DirectoryEntry classes to create queryable objects on the fly.
Support for DirectorySearcher in data source and context constructors enabling more flexibility for search options.
Updated samples to use the new available features.

Source code checked in, #12012

bdesmet — Thu, 31 Jul 2008 20:48:28 GMT

Refresh Release 1.0.1 - Includes bug fixes and support for: - byte[]- and GUID-valued directory attributes - Bug fix for non-constant EndsWith, BeginsWith and Contains clauses - Introduction of DirectoryContext with support for nested contexts and direct update support - Updated samples to use the new available features

Commented Issue: Suggestion: Making fields like pwdLastSet usable

bdesmet — Thu, 31 Jul 2008 12:29:33 GMT

I needed to be able to filter based on pwdLastSet in a query using LINQ to AD and using the SearchResult to get values instead of a DirectoryEntry made this possible. Attached is my patch for LINQ to AD that modifies DirectoryQuery.GetResults and DirectoryQuery.AssignResultProperty slightly to use the SearchResult object directly for most property lookups to allow automatic marshalling.
Comments: ** Comment from web user: bdesmet **

Thanks for your feedback. This will be adressed in the 1.0.1 Refresh Release.

Thanks,
-Bart

Commented Issue: Error when using parameters inside where clause

bdesmet — Thu, 31 Jul 2008 12:17:02 GMT

I was playing around with your demo project and substituted static string text by a variable, so for example:

string test = "A";
var res6 = from grp in groups
where grp.Name.StartsWith(test) <-- NOTE: Here I replaced static text with test variable
select new { grp.Name, MemberCount = grp.Members.Length };

Now I get the error 'System.NullReferenceException was unhandled', the error occurs at case statement:

case "StartsWith":
{
ConstantExpression c = m.Arguments[0] as ConstantExpression;
sb.AppendFormat("{0}={1}*", GetFieldName(o.Member), c.Value); <--- EXCEPTION: on variable 'c'
break;
}

By the way thanks for this Linq class!! Excellent work!

Yours sincerely,

Evert Wiesenekker
Comments: ** Comment from web user: bdesmet **

This issue will be resolved in the 1.0.1 Refresh Release.

Thanks for the feedback,
-Bart

Commented Issue: Suggestion: Add settings for PageSize and ClientTimeout

bdesmet — Thu, 31 Jul 2008 12:16:34 GMT

This implementation has a drawback which might cause queries to fail unneccesarily. To fix this I suggest that settings for PageSize and ClientTimout are added to allow search pagning against the directory. This will enable retrieving more than a 1000 enties at one time and allow retrieving data from slow servers. I have attached a new version of DirectorySource.cs which implements these changes.
Comments: ** Comment from web user: bdesmet **

The 1.0.1 Refresh Release will have support for AsQueryable<T> on a given DirectoryEntry or DirectorySearcher object, so that search parameters can be lifted into the query. In addition we'll provide a constructor overload that takes in a DirectorySearcher object that will be used to base the query parameters on, giving access to all the properties of DirectorySearcher rather than just the two mentioned in this suggestion.

Thanks for the feedback,
-Bart

Commented Issue: Problem to get System.Byte[] type properties.

bdesmet — Thu, 31 Jul 2008 12:15:10 GMT

First of all I want to congratuate you on this great job. But I met some worries with getting properties which type is System.Byte[] as objectGUID property. LinqToAD throws an unhandled exception: System.InvalidCastException: Object cannot be stored in an array of this type. (in AssignResultProperty method). Any idea ?
Comments: ** Comment from web user: bdesmet **

Mapping support for Guid types will be provided in the 1.0.1 Refresh Release.

Thanks for the feedback,
-Bart

Created Issue: Suggestion: Making fields like pwdLastSet usable

NeilW — Mon, 14 Jul 2008 18:12:49 GMT

New Post: StartsWith errors if using a parameter

pwalke — Tue, 01 Jul 2008 20:57:21 GMT

This is a known issue. Use the remedy disussed here

Commented Issue: Error when using parameters inside where clause

pwalke — Tue, 01 Jul 2008 20:56:34 GMT

I can confirm that this works. I'd be happy to merge these changes VIA team explorer in if I'm added as a developer to the project.

New Post: StartsWith errors if using a parameter

csrtjones — Fri, 13 Jun 2008 13:15:40 GMT

Hi,

First, this library a great idea and really appreciated.

We were attempting to create an autocomplete textbox and were trying to use the StartsWith LINQ operator:

public

static List<Group> GetGroups(string startsWith)

{

if (String.IsNullOrEmpty(startsWith)) throw new ArgumentException("startsWith cannot be null or empty.");

var ADGroups = new DirectorySource<Group>(Config.LDAPDirectoryEntry, SearchScope.Subtree);

var groups = ADGroups.Where(g => g.Name.StartsWith(startsWith)).Select(c => new Client { Name = g.Name, DateCreated = g.DateCreated, DateUpdated = g.DateUpdated });

return groups.ToList();

}

However, when passing the StartsWith parameter as a parameter the string somehow gets passed as a property of an object within DirectoryQuery...

ConstantExpression

c = m.Arguments[0] as ConstantExpression;

Where c.Value would normally contain the string passed as the parameter it now is c.Value.startsWith (being that I named the parameter as startsWith).

I tried debugging and correcting this, and also tried using reflection to dynamically access the property on c.Value, but I am unable figure this one out. Any ideas?

Thanks,
Ryan

COMMENTED ISSUE: Error when using parameters inside where clause

emargee — Fri, 30 May 2008 11:25:41 GMT

Just wanted to point out I had found a solution to this (after a lot of hair tearing out as this is a frustrating bug)

You can delete the line : ConstantExpression c = m.Arguments[0] as ConstantExpression;

and then replace c.Value with : (string) Expression.Lambda(m.Arguments[0]).Compile().DynamicInvoke()

.. it then works fine ! (found after much searching in a comment at the bottom of here: http://weblogs.asp.net/okloeten/archive/2007/10/03/4327290.aspx)

Hope this helps people trying to use this !

[mRg]

CREATED ISSUE: Error when using parameters inside where clause

Eefhert — Sun, 18 May 2008 19:17:58 GMT

CREATED ISSUE: Suggestion: Add settings for PageSize and ClientTimeout

Pontus — Thu, 15 May 2008 08:29:35 GMT

NEW POST: Getting securityIdentifier (sID)

raffaeu — Thu, 03 Apr 2008 12:50:35 GMT

It's works and also very fast and good!!
Thanks you solve me a lot of problem!

NEW POST: Getting securityIdentifier (sID)

csustek — Fri, 28 Mar 2008 18:16:12 GMT

Fixed it. But the solution is not intuitive.

It seems that you cannot use any other Type to define the objectSid other than "object". So in order to get teh actual sID, I added another property. Unfortunately, you cannot have ANY other properties on a type with the DirectorySchema attribute that does not exist in AD (it will throw an exception indicating that the property can't be found). This is OK; just add the DirectoryAttribute again with the same property name, but don't define anything in the set block.

DirectorySchema("user", typeof(IADsUser))
public class ADUser*
{
DirectoryAttribute("objectSid")
public object rawsID { get; set; }

DirectoryAttribute("objectSid")
public object sID
{
get
{
SecurityIdentifier s = null;

try
{
if (rawsID != null)
s = new SecurityIdentifier((Byte[])rawsID, 0);
}
catch { }

return s.ToString();
}
set
{

}
}
}

NEW POST: Getting securityIdentifier (sID)

csustek — Wed, 05 Mar 2008 22:58:43 GMT

I cannot seem to get the securityIdentifier. Here is my code for my property:

DirectoryAttribute("securityIdentifier")
public string sID { get; set; }

What am I doing wrong?

NEW POST: Method or operation is not implemented.

msr79 — Wed, 05 Mar 2008 18:56:02 GMT

Thanks Bart! I'll try that as a work around and see how it goes. Good job on this project thus far. I am liking it a lot.