Re: ...
Cant see what the problem is personally.
===>
There are no guidelines to dis/encourage the use of certain features. Ok, i understand the need of it for conversion purposes etc, but i see now that some companies uses the 'features' as the pro-method of doing things in vb.net 2003...
For some reason the support for old legacy code is still supported in the new VB.Net 2005 version. It is one thing to support it form Vb6 to VB.Net 2003, and not to mark every piece of 'smelly' code as obsolete, or give warning, but still supporting it in VS.Net 2005 + versions is not something...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.