Yeah, a little bit anyway. You know as well as I do that topics are only new for so long. After that, they should be taken as a given that 80%-90% of the people know already with proficiency.

I have to admit that, while some topics, like basic OO techniques have value and I believe will continue to have value, others should be retired. I think it's time for all of us to start researching "fresh" ideas and topics to present. Otherwise, we're likely to fall behind.


>You mean, something a little more refreshing and new than many of the topics that are constantly re-hashed....
>
>
>
>
>
>
>>I know, it's really neat. I've just completely encrypted an entire XML document and persisted it as a file on the hard drive. Absolutely amazing. Next time calls for speakers go out, you can bet that I'll be proposing some sessions on this one.
>>
>>>No I have not, but upon receipt of your post, I did peruse the docs.
>>>
>>>I guess this shows just how far reaching .NET is...
>>>
>>>Training is going to be a big issue. IMO, you could probably create a 2-3 day seminar on this topic alone. Perhaps even a 5 day training class!
>>>
>>>
>>>
>>>>BTW John,
>>>>
>>>>Have you taken a look at the System.Security.Cryptography namespace? There's some really cool stuff in there...
>>>>
>>>>>>
>>>>>One thing that strikes me: if you look at it from the right point of view, now with .NET, it seems that each language has become much less important versus the overall functionality granted by the CLR.
>>>>>>
>>>>>
>>>>>Precisely my point why one language should not be propped up over another as a GENERAL rule...