Mehyar Posted December 8, 2003 Posted December 8, 2003 Hello guys, IsNumeric is a VB6 Function that is still supported in .NET but I wonder isn't there an inherent .NET function that replaces it. Not the Char.Isnumber or Char.IsDigit, something for a string ... Quote Dream as if you'll live forever, live as if you'll die today
Leaders dynamic_sysop Posted December 8, 2003 Leaders Posted December 8, 2003 there's the char version .IsNumber as you say , but apart from that you can still use IsNumeric. i saw an article on msdn giving an example of IsNumeric for vb.net , which is basically the same as for vb6 but apart from that i dont think there's any other built in feature. Quote
*Gurus* divil Posted December 9, 2003 *Gurus* Posted December 9, 2003 There is no direct framework equivalent in .NET 1.1 - this has been implemented in .NET 2.0 where all numeric types have a TryParse method that does not rely on trapping an exception. Quote MVP, Visual Developer - .NET Now you see why evil will always triumph - because good is dumb. My free .NET Windows Forms Controls and Articles
Mehyar Posted December 9, 2003 Author Posted December 9, 2003 Thx divil for that... .NET 2.0 .. Is that Visual Studio .NET 2004 ? Quote Dream as if you'll live forever, live as if you'll die today
AndreRyan Posted December 29, 2003 Posted December 29, 2003 Possibly, it could be for "Orcas"(2005), I think "Whidbey"(2004) uses .Net 1.2 from what I've seen[Divil was probably referring to Whidbey]. .Net 2.0 will probably come in for Windows Longhorn, since they would have needed to alter the entire framework to be compatible with the complete rewriting of Windows, and since Windows itself is written in .Net there are now many more things you can do with .Net so it would be a version 2.0. I'm not 100% sure however, my belief that "Whidbey" uses .Net 1.2 is that I downloaded a pack of PDC ScreenSavers and they all came up with "Framework version 1.2 required" when you tried to run them(Since the people at the PDC were given free, incomplete, versions of Visual Studio 2004, I assume that's what they were made with). Quote .Net allows software to be written for any version of Windows and not break like Unmanaged applications unless using Unmanaged procedures like APIs. If your program uses large amounts of memory but releases it when something else needs it, then what's the problem?
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.