I am quite new to C #, so please support me. I am developing a small server application that includes event-driven server threads and GUI threads. I would like to create GUI and server "free" (without using two processes) I mean by the GUI once it checks That if the server thread is running then it checks, if it does not, otherwise the server notifies the thread that the GUI thread is active and that GUI thread Air can leave and the server leaves the thread alive.
pseudocode:
starts the GUI {if (serverThread.isRunning) inform the server that GUI is active and make Start ServerThread} GUI exits ( Notify the server to confirm that the GUI is being terminated; exit GUI GUI} This is a difficult part of how to restart the GUI and inform the server that the GUI is alive .
For now I have to do this: Start the GUI and the GU Create and activate the thread server inside the e.threadik is active after leaving the GUI server, but I do not know how to be known in the context of ServerTreff when the GUI resumes.
GUI has an icon
Thanks for your time and answer.
< P> I would never like to use such a server, combining GUI and In the server logic one always has a bad idea from both design and user perspective. In your case, I would recommend making two separate executables. The first server and the second GUI will be the server, possibly for the Windows service, for communication between the two, the WCF will be perfect, it allows you to create a communication channel on each side without any developer overhead.
I understand your concern of dividing two. But if you were a better and more experienced developer (and possibly an administrator), then you would think that separating the two is not logical, but the only way to reality solves your problem.
Comments
Post a Comment