CODEWITHSUNDEEP
c++cwindowswindows-shellsingle-instance
Wienczny
Wienczny

Reputation: 4205

Restrict application to one instance per shell session on Windows

There are a lot of solutions for restricting an application from running twice. Searching by process name, using a named mutex etc. But I all of these methods don't work if I want to restrict my application to the shell session.

A user may have more than login session and shell on windows (right?)? If this is true I want to be able to run one instance of my application in every shell session but allow only one.

Is there a way to get a shell identifier which could then be put into the mutex name?

Upvotes: 0

Views: 2134

Answers (4)

x4u
x4u

Reputation: 14077

If you want to restrict it to one instance per login session, even if the same user account has multiple login sessions running at the same time (Server/Terminal Server) you could use the handle from GetShellWindow to check if there is a instance running already for this desktop.

Upvotes: 0

John Knoeller
John Knoeller

Reputation: 34198

You can go from process id of the current process to a WTS session ID, I think that will do what you need. ProcessIdToSessionId

You should be aware that a terminal services session can be disconnected from one desktop and then connected to by another, so the 'shell' can actually change, but the session ID should remain the same.

Upvotes: 0

Patrick
Patrick

Reputation: 23629

You can create local (session only) or global (whole system) mutexes. See http://msdn.microsoft.com/en-us/library/system.threading.mutex.aspx for more info. Look for global and local.

Upvotes: 5

Byron Whitlock
Byron Whitlock

Reputation: 53921

The shell identifier you want to use is the user name. This is available as Environment::UserName or GetUserName()

Upvotes: 0

Related Questions