Actually, while getting involved in this thread, I realized that this would make a cool whitepaper also. I'll get it on the schedule...

If David is reading - I'll see if I can find someone interested in doing an article on this.

yag

>Ahh... That does help.
>
>Is there any detail on this anywhere - ie - a list of intrinsic vs extrinsic functions/methods?
>
>Finding things using intellisense works - using the assumption that if it's not there, it's an intrinsic method (or I just couldn't find it), but it would be nice to have a simple alphabetic reference.
>
>Alan
>
>>Actually, I did forget while typing that message - but it doesn't affect my response. <g>
>>
>>Let me explain in some more detail. There are two types of functions here - intrinsics and externals. CInt and CStr are intrinsics - so they cannot be called by C# or any other language. Other functions like UCase are external, and can be called by other languages. To make things a little more confusing, some of our intrinsics, in some cases, may call helper functions that are in the microsoft.visualbasic namespace - and C# developers could find them and call them - though I don't think they are documented (though intellisense should still work).
>>
>>I get the feeling that I just made things clear as mud. <g>
>>
>>yag
>>
>>>Alan,
>>>
>>>>The thing is, I was looking over this thread and noticed that YAG had pointed out that C# had access to the Framework for things like the Convert class while VB had conversion routines built in that might actually be faster. For instance, Convert.ToInt32(LongVar) vs CInt(LongVar).
>>>
>>>Maybe YAG forgot? :-)