Results for "Author: sabro"
After seeing a few examples submitted attempting to prevent more than one instance. I decided to submit my version. This code will only prevent the 2nd instance from running no matter what directory both .exe are executed from. In addition, it does not use App.PrevInstance and will not bring the 1st instance to the front, just merely a *WORKING* example of how to stop more then one instance from running and the code is very easy to understand and use in your own apps.
After seeing a few examples submitted attempting to prevent more than one instance. I decided to submit my version. This code will only prevent the 2nd instance from running no matter what directory both .exe are executed from. In addition, it does not use App.PrevInstance and will not bring the 1st instance to the front, just merely a *WORKING* example of how to stop more then one instance from running and the code is very easy to understand and use in your own apps.
After seeing a few examples submitted attempting to prevent more than one instance. I decided to submit my version. This code will only prevent the 2nd instance from running no matter what directory both .exe are executed from. In addition, it does not use App.PrevInstance and will not bring the 1st instance to the front, just merely a *WORKING* example of how to stop more then one instance from running and the code is very easy to understand and use in your own apps.
After seeing a few examples submitted attempting to prevent more than one instance. I decided to submit my version. This code will only prevent the 2nd instance from running no matter what directory both .exe are executed from. In addition, it does not use App.PrevInstance and will not bring the 1st instance to the front, just merely a *WORKING* example of how to stop more then one instance from running and the code is very easy to understand and use in your own apps.
After seeing a few examples submitted attempting to prevent more than one instance. I decided to submit my version. This code will only prevent the 2nd instance from running no matter what directory both .exe are executed from. In addition, it does not use App.PrevInstance and will not bring the 1st instance to the front, just merely a *WORKING* example of how to stop more then one instance from running and the code is very easy to understand and use in your own apps.