Click here to Skip to main content
4.47 / 5, 24 votes

1

2
1 vote, 10.0%
3
1 vote, 10.0%
4
8 votes, 80.0%
5

CSingleInstance - Single Instance Apps

By PJ Naughter | 3 Mar 2000
An MFC class to implement single instance apps.

Introduction

Welcome to CSingleInstance, a freeware MFC class to make your app into a single instance. Limiting your app to single instance is more tricky in Win32 with the removal of the hPrevInstance parameter from WinMain and the introduction of separate address spaces.

There are numerous examples already out there of making your app single instance, but some such as the one I found on http://www.codeguru.com/ require knowledge of undocumented or heavy duty MFC.

Other methods such as using FindWindow or FindWindowEx are not 100% bullet proof due to the preemptive Win32 environment.

This class internally uses a memory mapped file (MMF) into which the handle of the main window of your application is stuffed. When a second instance of your app is run, it detects that the memory mapped file exists, gets the window handle of the first instance from the MMF and reactivates the old window.

The source zip file contains the CSingleInstance source code and a simple MFC app (without Doc/View) which demonstrates all the functionality of the class. For further details on how to use the class, have a look at the BOOL CMyApp::InitInstance() function and the included documentation.

Features
Usage
History
API Reference
Contacting the Author

Features

  • Very simple API, only 2 functions exposed.
  • Does not require any messing around with window styles and your mainfrm source code.
  • Much more robust implementation than other methods as already mentioned.
  • The classes are fully Unicode compliant and include Unicode built options in the workspace file.

Usage

To use the class in your code, simply include sinstance.cpp in your project and #include sinstance.h in your app's source file. Create your mainfrm window as normal but before you show it, simply include the following code:

CMyApp::InitInstance()
{
    CInstanceChecker instanceChecker;

    if (instanceChecker.PreviousInstanceRunning())
    {
      AfxMessageBox(_T("Previous version detected, will now restore it"), 
                                                                   MB_OK);
      instanceChecker.ActivatePreviousInstance();
      return FALSE;
    }

    ....

    // create main MDI Frame window

    CMainFrame* pMainFrame = new CMainFrame;
    m_pMainWnd = pMainFrame;

    if (!pMainFrame->LoadFrame(IDR_MAINFRAME))
        return FALSE;

    // If this is the first instance of our App then

    // track it so any other instances can find it.

    if (!instanceChecker.PreviousInstanceRunning())
        instanceChecker.TrackFirstInstanceRunning();

    .....
}

That's all there is to it. Your application should now be single instance. For those interested in the nitty gritty of the code, have a look at sinstance.cpp.

History

  • V1.0 (29th July 1998)
    • Initial public release.
  • V1.01 (27th March 2000)
    • Now ships with a VC 5 workspace.
    • Fixed a potential handle leak where the file handle m_hPrevInstance was not being closed under certain circumstances.
    • The remaining changes were made by Neville Franks. Contact nevf@getsoft.com, http://www.getsoft.com/.
    • Changed #pragma error in instance header file to #pragma message. Former wouldn't compile under VC6
    • Replaced above #pragma with #include.
    • Added TrackFirstInstanceRunning(), MakeMMFFilename()
    • Split PreviousInstanceRunning() up into separate functions so we can call it without needing the MainFrame window.
    • Changed ActivatePreviousInstance() to return hWnd.
  • V1.02 (28th March 2000)
    • Minor update to the documentation.

API Reference

The API consists of the the two public member functions of the class CSingleInstance:

CSingleInstance::PreviousInstanceRunninging

BOOL CSingleInstance::PreviousInstanceRunning()

Return Value:

TRUE if a previous instance of this application is running, otherwise FALSE.

Remarks:

In response to TRUE being sent back the program, should call ActivatePreviousInstance() and abort prematurely from the current instance of the app.

CSingleInstance::ActivatePreviousInstance

BOOL CSingleInstance::ActivatePreviousInstance()

Remarks:

Activates the previous instance of the app as detected in a call to PreviousInstanceRunning().

Contacting the Author

PJ Naughter

Email: mailto:pjn@indigo..ie

Web: http://www.naughter.com/

29th July 1998

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

PJ Naughter




United States United States

Member


Sign Up to vote for this article
Add a reason or comment to your vote:

Comments and Discussions

You must Sign In to use this message board.
FAQ FAQ 
 
Noise Tolerance  Layout  Per page   
 Msgs 27 to 43 of 43 (Total in Forum: 43) (Refresh)FirstPrevNext
GeneralDefinition of "single instance" not complete PinsussDaniel Lohmann10:10 8 Apr '00  
GeneralRe: Definition of PinsussNeville Franks22:08 9 Apr '00  
GeneralRe: Definition of Single Instance PinsussMichael Tomlinson19:32 15 Mar '04  
GeneralRe: Definition of PinmemberJim Howard9:22 1 Dec '00  
GeneralRe: Definition of "single instance" not complete Pinmemberpjnaughter0:35 4 Apr '03  
GeneralRe: Definition of "single instance" not complete Pinmemberpjnaughter11:45 16 Mar '04  
GeneralRe: Definition of "single instance" not complete PinmemberDaniel Lohmann23:10 16 Mar '04  
pjnaughter wrote: This is not true (at least with the latest versions of my code), since you can specify the mutex name to use. That way the developer who uses the class can decide to specify a prefix of "Global\" or "Local\" so that they can decide which way they want to define the mutex. These extensions to the NT Name space with added to NT 4 Terminal Services edition and are a native part of Windows 2000
Right, but this leaves the problem still in the responsibility of the developer who uses your class. S/he still has to know about the subtle problems and to decide how to build a correct name.

Specifing the "Local\" or "Global\" prefix is, for instance, usually not enough. One point is, that it would fail on all (non-TS) systems prior to Win2k, because the backslash is an illegal character for kernel object names. Another point is, that it simply does not solve the issue. (Or lets say: It solves only part of the issue.)
If the programmer was responsible enough to use the "Local\" prefix (or no prefix at all, as "Local\" is the default inside a TS session) I can start the app in different TS sessions.
Fine. But the execution (via RunAs) of a second instance as another user in the *same* TS session is still prohibited. Does this really make sense? IMHO, this makes sense only in very few application scenarios.

As a developer: If I use a "ready-to-use" class for the instance check (especially if it is from PJ Naughter Wink ), I would expect it to deal with the critical cases on its own, instead of delegating me the job to create the "right" kernel object name for the intended instance-restriction.

You may want to take a look into my instance-check code at http://www.losoft.de/code/SingleInstance.zip. It is a more C-stylish solution, but shows how to create the different names. Please free to incorporate it into your class Big Grin

--

Daniel Lohmann

http://www.losoft.de
(Hey, this page is worth looking! You can find some free and handy NT tools there Big Grin )
GeneralRe: Definition of "single instance" not complete Pinmemberpjnaughter4:31 17 Mar '04  
GeneralRe: Definition of "single instance" not complete Pinmemberpjnaughter9:36 9 May '04  
GeneralHow does this compare with just using a CMutex? PinsussJames White8:24 6 Apr '00  
GeneralRe: How does this compare with just using a CMutex? PinsussNeville Franks21:59 9 Apr '00  
GeneralDoesn't seem to work with dialog based apps PinsussNewbie19:13 4 Apr '00  
GeneralRe: Doesn't seem to work with dialog based apps PinsussPJ Naughter12:49 5 Apr '00  
GeneralRe: Doesn't seem to work with dialog based apps PinsussNewbie7:47 6 Apr '00  
GeneralRe: Doesn't seem to work with dialog based apps PinsussStephan Walbaum10:14 11 Apr '00  
GeneralRe: Like this it does work with dialog based apps PinsussStephan Walbaum7:40 19 Apr '00  
GeneralRe: Doesn't seem to work with dialog based apps PinsussPJ Naughter11:39 17 May '00  

General General    News News    Question Question    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+PgUp/PgDown to switch pages.

PermaLink | Privacy | Terms of Use
Last Updated: 3 Mar 2000

Copyright 2000 by PJ Naughter
Everything else Copyright © CodeProject, 1999-2010
Web18 | Advertise on the Code Project