T
Tom Dacon
I have a little desktop application (it happens to be a Windows Forms analog
clock) that's written in VB.Net (2003). I placed a shortcut in my Startup
program group to start it up when I log on. I have put no code in the
application whatsoever to do internet communications, and yet when it starts
up at logon I've begun getting notification dialogs from my software
firewall that the app wants to connect to the internet. It doesn't happen
when the app has been freshly rebuilt, but after a few days or so it starts
to try to connect and thereafter tries again each time the app is started
up.
Thinking that I might have acquired some new kind of virus that attaches
itself to .Net executables, I made a note of the file size and the 'last
modified' date after a fresh build, and then checked it again after the
executable started wanting to connect to the internet. No changes. Norton
AntiVirus 2003 with the most recent updates shows a clean scan. I always
tell the firewall (Norton Personal Firewall 2003) to block the
communication, and the application continues to execute normally.
Has anyone else seen similar behavior in non-communications-enabled
applications, or know of anything that might shed some light on this
behavior?
Thanks,
Tom Dacon
Dacon Software Consulting
clock) that's written in VB.Net (2003). I placed a shortcut in my Startup
program group to start it up when I log on. I have put no code in the
application whatsoever to do internet communications, and yet when it starts
up at logon I've begun getting notification dialogs from my software
firewall that the app wants to connect to the internet. It doesn't happen
when the app has been freshly rebuilt, but after a few days or so it starts
to try to connect and thereafter tries again each time the app is started
up.
Thinking that I might have acquired some new kind of virus that attaches
itself to .Net executables, I made a note of the file size and the 'last
modified' date after a fresh build, and then checked it again after the
executable started wanting to connect to the internet. No changes. Norton
AntiVirus 2003 with the most recent updates shows a clean scan. I always
tell the firewall (Norton Personal Firewall 2003) to block the
communication, and the application continues to execute normally.
Has anyone else seen similar behavior in non-communications-enabled
applications, or know of anything that might shed some light on this
behavior?
Thanks,
Tom Dacon
Dacon Software Consulting