Not necessarily true. The VB runtime DLL is the standard VB function
library, and IsDate/IsNumeric are part of that library.
The functionality that has been depreciated and/or was built specifically
for easing migration lives in the Compatibility DLL.
The BIG difference is that the VB function library is not depreciating.
Also, there is *no* direct alternative to these functions in the runtime
library. If you use ILDasm to see this implementation, you will notice that
these functions do a lot more than the Parse() methods available on double
and DateTime. VB's runtime library is a tremendous convenience. Who would
want to keep writing these functions over and over? And more to the point,
if you created your own library for them, it'd be no different.
-Rob Teixeira [MVP]
"Marina" <so*****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
I didn't remember exactly where it was and didn't bother to look it up. My
point was that it was in a DLL created specifically to make VB6 to VB.NET
transition easier.
"Armin Zingler" <az*******@freenet.de> wrote in message
news:en****************@TK2MSFTNGP11.phx.gbl... "Cor" <no*@non.com> schrieb Hi Armin,
Yes but that is not completly clear from your message.
You only say "sure ?" and not that they are normal in the
Microsoft.VisualBasic namespace
After writing "sure?" I think she will see where it actually is.
--
Armin