Quote:
|
Originally Posted by Ooble
The way I do it is the way Microsoft recommend. I don't know if it's the most efficient, but you can be sure it's the easiest to understand and debug.
|
Link? I'm just curious why Microsoft would recommend your approach. I'm not saying it's a bad way to implement it because it obviously works.
I may be reading into the original post, but I thought the Password form was going to be implemented like a dialog, meaning that if there wasn't a password already "auto-saved" (ie in a text file) that the program should popup the Password Form and then Dispose(...) the password form and popup the main form (assuming authentication was successful)
With your approach, it'll popup the password form and then immediately exit because you haven't used Application.Run(...) so your program doesn't have a message pump.
Although, I'm sure your example can be modified to support that if that's what the original poster wanted.