I have constantly maintained that End has its place. The only problem with End, as far as I know, is that it prevents any code you might have written from being automatically run before your program exits. If that's what you actually want, then End can be immensely useful.
David Crowell wrote:
It should have been removed. End is the absolute worst way to end an application. This has been rehashed many times since the early days of VB.
Dave
Seth Sticco wrote:
Doesn't VB.NET still have the End statement?
..yep, it does - I just double-checked. I'd be using that to get the effect you described. By the way, it apparently calls System.Environment.Exit, so just calling that should do the same thing.
=================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in:
Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet
View archives and manage your subscription(s) at http://discuss.develop.com
=================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in:
Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet
View archives and manage your subscription(s) at http://discuss.develop.com
