Connection Manager API

Hi,

I've seen some comment at various places on some sort of managed wrapper for
the connection manager API that's now available in .NetCF 3.5. Can anyone
shed a little more light on this like a) yeah it's in there and b) you need
to look in the XXX.xxx.xxx namespace.

Help appreciated.
J

Apparently, the page I found that said that it was wrapped in .NET CF 3.5
was in error. Of course, you can P/Invoke it or you can use OpenNETCF.

Paul T.

"JonnyM" <JonnyM@discussions.microsoft.com> wrote in message
news:E4A78D7E-051E-4A4B-B29A-B70FBE9BAF7A@microsoft.com...
> Hi,
>
> I've seen some comment at various places on some sort of managed wrapper
> for
> the connection manager API that's now available in .NetCF 3.5. Can anyone
> shed a little more light on this like a) yeah it's in there and b) you
> need
> to look in the XXX.xxx.xxx namespace.
>
> Help appreciated.
> J

Thanks Paul. Must admit I was coming to that conclusion. I guess I'll be
going the P/Invoke route.

"Paul G. Tobey [eMVP]" wrote:

> Apparently, the page I found that said that it was wrapped in .NET CF 3.5
> was in error. Of course, you can P/Invoke it or you can use OpenNETCF.
>
> Paul T.
>
> "JonnyM" <JonnyM@discussions.microsoft.com> wrote in message
> news:E4A78D7E-051E-4A4B-B29A-B70FBE9BAF7A@microsoft.com...
> > Hi,
> >
> > I've seen some comment at various places on some sort of managed wrapper
> > for
> > the connection manager API that's now available in .NetCF 3.5. Can anyone
> > shed a little more light on this like a) yeah it's in there and b) you
> > need
> > to look in the XXX.xxx.xxx namespace.
> >
> > Help appreciated.
> > J
>
>
>

As Paul says, I can confirm there is no Connection Manager .NET wrapper in
the .NET CF 3.5, sadly.
--
Simon Hart
Visual Developer - Device Application Development MVP
http://simonrhart.blogspot.com


"JonnyM" wrote:

> Hi,
>
> I've seen some comment at various places on some sort of managed wrapper for
> the connection manager API that's now available in .NetCF 3.5. Can anyone
> shed a little more light on this like a) yeah it's in there and b) you need
> to look in the XXX.xxx.xxx namespace.
>
> Help appreciated.
> J