<dumchikov@gmail.com> wrote in message
news:1130849857.304743.257580@g44g2000cwa.googlegroups.com...
> Hi,
>
> I have implemented the IADs interface in .NET. And I want to use
> System.DirectoryServices.DirectoryEntry class with my implementation.
> The DirectoryEntry has the constructor DirectoryServices(Object obj).
> So I supposed, that I can use it if I passed my implementation there.
> But the ArgumentException was thrown when I called the cunstructor.
> Then I used Reflector to see this constructor and found the code, which
> thrown the exception. It was something like this:
>
> this.adsObject = adsObject as UnsafeNativeMethods.IAds;
> if (this.adsObject == null)
> {
> throw new
> ArgumentException(Res.GetString("DSDoesNotImplementIADs"));
> }
>
> My question is why my implementation of the IADs couldn't be cast to
> the UnsafeNativeMethods.IAds? After all, they are the same.
>

>
> IAds is a COM native interface, how did you manage to get your version
> registered correctly?
> Also, I'm not clear what language was used to implement your version? .Net
> is not a language it's a ... well it's actualy a marketing term ;-).
>
> Willy.

> >Yes, I know that IADs is a COM interface. But I can implement this
> >interface and other ADSI interfaces using C#,
>
> Yes, but why would you even bother to do so? System.DirectoryServices
> with DirectoryEntry and DirectorySearcher is much easier to use in the
> first place..... why create potential problems with interop and stuff
> like that when you could use the out-of-the-box .NET components
> instead?
>
> Marc
> ================================================================
> Marc Scheuner May The Source Be With You!
> Berne, Switzerland m.scheuner -at- inova.ch

<dumchikov@gmail.com> wrote in message
news:1131002147.277661.193650@g14g2000cwa.googlegroups.com...
>> >Yes, I know that IADs is a COM interface. But I can implement this
>> >interface and other ADSI interfaces using C#,
>>
>> Yes, but why would you even bother to do so? System.DirectoryServices
>> with DirectoryEntry and DirectorySearcher is much easier to use in the
>> first place..... why create potential problems with interop and stuff
>> like that when you could use the out-of-the-box .NET components
>> instead?
>>
>> Marc
>> ================================================================
>> Marc Scheuner May The Source Be With You!
>> Berne, Switzerland m.scheuner -at- inova.ch
>
> Yes the DirectoryServices namespace is quite useful.
> The thing is that I need to implement my own ADSI provider on .NET. So
> I did following things:
>
> 1) Created description of IADs
>
> [ComImport]
> [InterfaceType(ComInterfaceType.InterfaceIsDual)]
> [Guid("FD8256D0-FD15-11CE-ABC4-02608C9E7553")]
> public interface IADs
> {
> // Properties and methods
> }
>
> 2) Implemented this interface
> internal class ADsObject : IADs
> {
> // implementation
> }
>
> 3) Tried to use the implementation
>
> ADsObject obj = new ADsObject("adsPath");
> DirectoryEntry entry = new DirectoryEntry(obj);
>
> But the ArgumentException was thrown in the last line.
> That's the problem.
>

>Yes, I know that IADs is a COM interface. But I can implement this
>interface and other ADSI interfaces using C#,