Feb 7, 2010
I successfully coded MyApplication_Startup and MyApplication_StartupNextInstance to give my single-instance application access to the command line. It works fine. if the application is not running and the user double clicks on a filetype associated with my application, my application starts up and reads in the file that was double clicked on. That's fine.
View 1 Replies
However, when the user double clicks on another file (same associated type) when the application is already running, I then (and only then) get a warning (from McAfee in my case) that my application is requesting access to the internet. I simply click OK to allow access, McAfee goes away, focus shifts to the original instance, and that instance successfully reads in the second file.
If the user then double clicks on a third file when the application is already running, focus shifts to the running application, it loads the third file, and the internet access warning DOES NOT appear. Same with all subsequent cases.
Any ideas about why the sudden internet access warning is occuring? In all the startup and load events, I do not do any internet related things. Much later, the program will send an email, but that code is far removed from Startup and Load things.My only idea is that perhaps because I have "awakened" the normally hidden ApplcationEvents.vb file (by putting some code in there), maybe I have triggered some sort of handling of the MyApplication_NetworkAvaialabilityChanged event, even though I make no reference to this event anywhere.
Before I added the command line handling stuff, I noticed that the internet access warning would occur only once for each new build. Susequent execution of the same build would not trigger an internet access warning. So now it is as if the handling of the StartupNextInstance event is simulating starting up a new build for the first time. Weird.
One more thing. I am not deploying this over a network. I am making a simple .exe by selecting Build from the MVS 2008 menu, then running the .exe by double clicking on it from Windows Explorer. I am using Visual Basic 2008 Express on Windows XP.