Limit C# console app to one instance

[JS]

Using Visual Studio 2008 I want to prevent myconsoleapp.exe from
executing multiple times on a given Windows host.

The desire is, if a user launches myconsoleapp.exe a second time the
second instance dies because there is already one myconsoleapp.exe
running. Ideally the user would not be able to rename myconsoleapp.exe
to, for example, myconsoleapp2.exe and fire that up either.

Is this possible and any pointers or tips for doing so?

[Michael Justin]

JS wrote:

Using Visual Studio 2008 I want to prevent myconsoleapp.exe from
executing multiple times on a given Windows host.

I am quite sure that there is a "Mutex" class somewhere in the .NET
library which can be used to provide a system-wide flag. The second app
would detect that the flag is already set by the first (running) app and
then will quit.

This is basically the same technique used by installer applications to
detect if there is an old version of the application running.

Hope this Helps(tm)
--
Michael Justin
SCJP, SCJA
betasoft - Software for Delphiâ„¢ and for the Javaâ„¢ platform
http://www.mikejustin.com - http://www.betabeans.de

[kimiraikkonen]

On May 23, 7:11 pm, JS <JSwrote:

Using Visual Studio 2008 I want to prevent myconsoleapp.exe from
executing multiple times on a given Windows host.

The desire is, if a user launches myconsoleapp.exe a second time the
second instance dies because there is already one myconsoleapp.exe
running. Ideally the user would not be able to rename myconsoleapp.exe
to, for example, myconsoleapp2.exe and fire that up either.

Is this possible and any pointers or tips for doing so?

Mutex is a choice and you can also consider checking the option
through Solution Explorer -application properties -Windows
Application Framework Properties -Make single instance application.
(Can't confirm exact path for 2008, currently have 2005)

Thanks,

Onur Güzel

[kimiraikkonen]

On May 23, 7:44 pm, kimiraikkonen <[e-mail]:

On May 23, 7:11 pm, JS <JSwrote:

Using Visual Studio 2008 I want to prevent myconsoleapp.exe from
executing multiple times on a given Windows host.

The desire is, if a user launches myconsoleapp.exe a second time the
second instance dies because there is already one myconsoleapp.exe
running. Ideally the user would not be able to rename myconsoleapp.exe
to, for example, myconsoleapp2.exe and fire that up either.

Is this possible and any pointers or tips for doing so?

Mutex is a choice and you can also consider checking the option
through Solution Explorer -application properties -Windows
Application Framework Properties -Make single instance application.
(Can't confirm exact path for 2008, currently have 2005)

Thanks,

Onur Güzel

Sorry, ignore my second advice(Make single instance option), it is
applicable in VB not in C#...

Thanks,

Onur Güzel

[j1mb0jay]

On Fri, 23 May 2008 12:11:22 -0400, JS wrote:

Using Visual Studio 2008 I want to prevent myconsoleapp.exe from
executing multiple times on a given Windows host.

The desire is, if a user launches myconsoleapp.exe a second time the
second instance dies because there is already one myconsoleapp.exe
running. Ideally the user would not be able to rename myconsoleapp.exe
to, for example, myconsoleapp2.exe and fire that up either.

Is this possible and any pointers or tips for doing so?

http://www.codeproject.com/KB/cs/CSSIApp.aspx

Hope that helps.

j1mb0jay

[Michael Justin]

j1mb0jay wrote:

http://www.codeproject.com/KB/cs/CSSIApp.aspx

"Single-Instance C# Application - for .NET 2.0"

This looks interesting, however it seems to force the developer to use
Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase
for the main class, so imho this is not a "lightweight" solution.

But it at least this is a nice example how .NET allows to mix libraries
from different language 'universes'.
I would recommend Mutex, which I have found here:

http://msdn.microsoft.com/en-us/libr...ing.mutex.aspx

A nice thing is that Mutex supports "global" and "local" visibility in
terminal services environments. So two different sessions are not able
to launch the same application - this can be a real life-saver for some
apps.
Best Regards
--
Michael Justin
SCJP, SCJA
betasoft - Software for Delphiâ„¢ and for the Javaâ„¢ platform
http://www.mikejustin.com - http://www.betabeans.de

[harborsparrow]

On May 25, 5:15 am, Michael Justin <[e-mail]:

j1mb0jay wrote:

http://www.codeproject.com/KB/cs/CSSIApp.aspx

"Single-Instance C# Application - for .NET 2.0"

This looks interesting, however it seems to force the developer to use
Microsoft.VisualBasic.ApplicationServices.WindowsF ormsApplicationBase
for the main class, so imho this is not a "lightweight" solution.

But it at least this is a nice example how .NET allows to mix libraries
from different language 'universes'.

I would recommend Mutex, which I have found here:

http://msdn.microsoft.com/en-us/libr...ing.mutex.aspx

A nice thing is that Mutex supports "global" and "local" visibility in
terminal services environments. So two different sessions are not able
to launch the same application - this can be a real life-saver for some
apps.

Best Regards
--
Michael Justin
SCJP, SCJA
betasoft - Software for Delphi™ and for the Java™ platformhttp://www.mikejustin.com-http://www.betabeans.de

Place "using System.Threading;" at the top of the file, and include
this code in the Main:

1: // do not allow to run twice
2: bool ownsMutex; Mutex mutex = null;
3: try
4: {
5:
6: mutex = new Mutex(false, Application.ProductName,
out ownsMutex);
7: if (!ownsMutex)
8: {
9: Console.Writeline(Application.ProductName + "
is already running.");
10: return;
11: }
12: GC.KeepAlive(mutex);
13: }
14: catch
15: {
16: }

[Jon Skeet [C# MVP]]

On May 27, 3:14 am, harborsparrow <[e-mail]:

Place "using System.Threading;" at the top of the file, and include
this code in the Main:

<snip>

I wouldn't advise using exactly that code: including an empty
exception handler is never a good idea. But yes, it's on the right
lines.

Jon

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Jon Skeet [C# MVP] wrote:

On May 27, 3:14 am, harborsparrow <[e-mail]:

>Place "using System.Threading;" at the top of the file, and include
this code in the Main:

<snip>

I wouldn't advise using exactly that code: including an empty
exception handler is never a good idea.

Very true.

But hopefully readers of m.p.d.l.cs will understand that
posted code represent ideas and not production ready code.

(on the other hand then just omitting the catch entirely
would have made the point even simpler)

Arne