Problem with Environment.CommandLine routine.

I have an app that is controlled by a module to make sure it is only opened once. Now that works fine but the problem is if my app is open, and a command argument, Environment.CommandLine, is sent to it, nothing happens. The code below just shows the Module to open my app.

(Thanks to Yzlat for the following code)
_________________________________________________________
Module monitor
    Sub main()
        Dim bAppOwnership As Boolean = False
        Dim sAppName As String = "Local\" & Reflection.Assembly.GetExecutingAssembly.GetName.Name
        'Return value - contains true if the calling thread was granted initial ownership of the mutex.
        Dim bAppFirstInstance As Boolean
        'Static ensures the mutex is not garbage collected until the application is unloaded
        Static m As System.Threading.Mutex
        Try
            'Create mutex
            m = New Threading.Mutex(bAppOwnership, sAppName, bAppFirstInstance)
            'If this is the first instance of the mutex, then run the application
            If bAppFirstInstance Then Application.Run(New frmConfig)
        Catch ex As Exception
            'error - display a system modal error message box
            MsgBox(ex.Message, Microsoft.VisualBasic.MsgBoxStyle.SystemModal Or Microsoft.VisualBasic.MsgBoxStyle.Critical Or Microsoft.VisualBasic.MsgBoxStyle.OKOnly, _
            Application.ProductName & " Is Unable To Start. ")
        Finally
            m = Nothing
        End Try
    End Sub
End Module
____________________________________________________________________

Any ideas?
LVL 6
cjinsocal581Asked:
Who is Participating?
 
grayeConnect With a Mentor Commented:
How time critical is the switch to the new "context"?

A simple solution could be this:

1) When the application starts, it record the command line arguments to a common file (perhaps with a file lock or time stamp)
2) If the file already exists (or has a lock) then you know another instance is running and you can exit the current instance
3) Then the application periodically checks this file to see if the content has changed (perhaps by the time stamp).  If it has changed, then that's an indication to stop doing whatever-it-is-that-it's-doing and do something else.

That way this file now serves two purposes... to detect if an 2nd instance exists or not...and to communicate the "change in context" brought on by the 2nd instance's command line arguments.

This could be accomplished with something as simple as a multi-threaded timer looking for changes to the file or by something a bit more elegant (like using the FileSystemWatcher class)
0
 
grayeCommented:
Huh?  What's that got to do with command-line arguments?
0
 
cjinsocal581Author Commented:
Actually, EVERYTHING.

You see, the problem is that this "new" code (Above) that I added to my application DOES prevent any new instances from opening when the app is already opened. The problem is that I have a simple Environment.CommandLine argument that is sent to the app.

Now, when the application IS NOT open, and I send the Environment.CommandLine argument to it, it opens fine and processes the Environment.CommandLine argument. BUT, when the application IS already open, it will NOT accept any new arguments.

So, here is the scneario:

APP IS NOT OPEN:
Using the Run box. I type MyApp.exe -Information

App opens, processes "Information" into a listbox.

APP IS ALREADY OPEN:
Using the Run box. I type MyApp.exe -Information

NO new instance of the app opens (This is good) BUT DOES NOT process "Information"

Ideas?
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
grayeCommented:
OK, I understand now.  But this is not gonna be easy...

You'll have to have the 2nd instance of the program "talk to" the first instance (to tell it the change in the command line arguments).  The 1st instance would then stop doing whatever it's doing, and start doing whatever the new command line argument is asking it to do.  After that, the 2nd instance can just exit.

There are several methods of Inter Process Communication (IPC) that are available to VB.Net, but they are all a bit complicated.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipc/base/interprocess_communications.asp

This might seem like a crazy idea, but can you simply kill off the 1st instance and completely repace it with the 2nd instance (with the new command line arguments)?
0
 
cjinsocal581Author Commented:
Thanks for the response..

To answer your question about killing the current app: No - due to a number of things:

There is a status window in the app that logs all activity of the application, there is a splash window that opens each time the app runs, the app will usually sit in the system tray 99% of the time.
0
 
cjinsocal581Author Commented:
What if I create a second app that just does the monitoring of the CommandLine arguments and pass it to the app? (Plus check to see if it is already opened or not?)

I know this may walk us down that same path, but at least I can kill that one.... Let me know your thoughts
0
 
cjinsocal581Author Commented:
Good thoughts.... I will have to experiment.

Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.