Understood. However, there are two catches to using the
NegotiateStream.
The first is one that I am not really concerned about, but its worth
noting. Datagram (i.e. streamless protocols) would utilize a different
form of the SSPI interface so NegotiateStream wouldn't work.
The second one is simply about acceptance of .NET 2.0 in organizations.
Given the relatively recent crowning of 2.0 by Microsoft (didn't it go
gold in November), it may be more difficult to get acceptance of it as
the platform for critical projects.
Thank you for your fast response Joe, I do appreciate it!
Joe Kaplan (MVP - ADSI) - 02 Jan 2006 04:44 GMT
Only you can determine whether .NET 2.0 is right for you within the shipping
timeframe of your product. If the product is mostly server-based, getting
the framework deployed is usually no big deal. If you need a large client
deployment, any kind of deployment will be tricky.
You can always implement your own SSPI wrapper as well. In fact, I'm pretty
sure MS had a .NET remoting sample demonstrating how to do this for .NET 1.1
on their website. It doesn't help you with UDP necessarily though. I have
no idea what to suggest in that case.
Joe K.
> Understood. However, there are two catches to using the
> NegotiateStream.
[quoted text clipped - 9 lines]
>
> Thank you for your fast response Joe, I do appreciate it!