2

I have a .NET 2005 (C#) desktop application, in which there is a login form and an MDI form, which then have multiple subforms. All other forms are opened in MDI form only.

After a user logs in, I hide the login form and then show the MDI form, but when I close the MDI form, my application process does not end because the login form is still hidden. I want that, when the user closes the MDI form, the whole application should close (essentially, the process should not be shown in the task manager), because if everytime the user closes and reopens the application and logs in, it will create some performance problem.

I am doing something like below:

//my login validation script,

//after successful login

this.Hide();

if (globalData.ObjMdiMain.IsDisposed)
{
    globalData.ObjMdiMain = new mdiMain();
}
globalData.ObjMdiMain.Show();

globalData is my static class where I create global objects which are required by the whole application. There, I have defined the ObjMdiMain object of my MDI form and I am accessing it here in the login form.

So, is there any method or function which will end the whole process from system, something like "Application.End();" or something else?

Thanks!

Svante
  • 50,694
  • 11
  • 78
  • 122
djmzfKnm
  • 26,679
  • 70
  • 166
  • 227

7 Answers7

8

I assume from your description (please correct me if I'm wrong), that you have the login form set as your startup form, like this:

    static void Main() {
        Application.EnableVisualStyles();
        Application.SetCompatibleTextRenderingDefault(false);
        Application.Run(new LoginForm());
    }

Don't do that. Change it to something like this instead:

    static void Main() {

        Application.EnableVisualStyles();
        Application.SetCompatibleTextRenderingDefault(false);

        LoginForm frm = new LoginForm();
        if(frm.ShowDialog() == DialogResult.Cancel) {
            return;
        }

        Application.Run(new MdiForm());
    }

In your login form code, do not call the MDI form at all, just validate the username and password and allow the login form to exit. The Main method will then call the MDI form properly.

Your application will then exit naturally when you close the MDI form.

Christian Hayter
  • 30,581
  • 6
  • 72
  • 99
  • Yes, you are correct I have the login form as Start-up form, let me try out your code. – djmzfKnm Oct 27 '09 at 04:34
  • Hi @Christian, I have tested your code but I am getting this http://farm3.static.flickr.com/2480/4052283130_893d670f92_o.png error, when I am closing my login form with `this.Close()` after successful login check. – djmzfKnm Oct 28 '09 at 05:16
  • I am using Windows7 with VS2005. – djmzfKnm Oct 28 '09 at 05:17
  • Sorry Prashant, I can't access that URL. What is the error message text? – Christian Hayter Oct 28 '09 at 08:40
  • Christian: The image url is working properly, anyways; I am getting "System.Threading.SemaphoreFullException was unhandled" exception with message "Adding the given count to the semaphore would cause it to exceed its maximum count." – djmzfKnm Oct 28 '09 at 10:11
  • Prashant, could you post your `Main` method code and your login form code, and I'll see if I can see the problem. – Christian Hayter Oct 28 '09 at 10:56
  • Hey @Christian, thanks but my problem got resolved. Your code was right and perfect. Problem was at my end. I am connecting .NET app to MySQL db for which I am using MySQL .net connector: http://dev.mysql.com/downloads/connector/net/6.1.html but I was sing 5.1 version of this DLL whereas its now reached to 6.1 So It was problem with the MYSQL connector DLL, I have upgraded to new version and its working perfect. Thanks for your help and support. – djmzfKnm Oct 29 '09 at 16:25
1

I find it strange that you leave the login window hidden after the initial login. Why not close it? Then you would not have your current problem: after successful login you only have the main MDI window that when is closed exits the running Windows Forms application. Is there a reason you hide the login window instead of closing it?

peSHIr
  • 6,279
  • 1
  • 34
  • 46
  • Because `Login` is the main form of the application, when I am closing this then its ending the whole application. – djmzfKnm Oct 26 '09 at 08:59
  • I concur with Christian Hayter: don't use the default project structure of simply running a default form, but write your own startup code. Also see http://stackoverflow.com/questions/406385/handling-unhandled-exceptions-problem#406473 for an example that takes top level fatal exception handling into account. Your login GUI logic would go in place of the `// whatever you need/want here` in my example. – peSHIr Oct 26 '09 at 09:50
1

I presume you've looked at Application.Exit?

Samuel Jack
  • 32,712
  • 16
  • 118
  • 155
0

There is Application.Exit() which will send a windows message to close all forms and exit the message loop.

Andrew Keith
  • 7,515
  • 1
  • 25
  • 41
0

I hate to break it to you, but... Application.Exit() is what you're asking for. Had you actually tried, you would have found it. Though, I have to agree with peSHIr, why are you keeping the login form around if it's causing you issues?

Matthew Scharley
  • 127,823
  • 52
  • 194
  • 222
0

Here is a maner of closing the actual process, but it is the bad way to close an application :

Environment.Exit(Code)

you can set the code at 0. or other integer, this will tell windows wath is the result of execution of the application.

I advise you to close the login form first and then shut down your application, this is the proper way.

Good luck ;)

H2.
  • 1
  • 1
0

It seems a MySql .net connector bug, because I was using mysql .net connector DLL to connect to my mysql db. I have seen some other complains about it too. See http://bugs.mysql.com/bug.php?id=36688

I was using MySQL .net connector DLL of version 5.1, I have just upgraded to 6.1 (latest) and its working fine without any error.

Download the latest DLL here: http://dev.mysql.com/downloads/connector/net/6.1.html

Thanks

djmzfKnm
  • 26,679
  • 70
  • 166
  • 227