Does anyone have McAfee firewall (specifically the free AOL version, but could be any version) and also Visual Studio 2005 installed?
I am trying to pinpoint what might be a framework bug, but I need some additional people to test.
Printable View
Does anyone have McAfee firewall (specifically the free AOL version, but could be any version) and also Visual Studio 2005 installed?
I am trying to pinpoint what might be a framework bug, but I need some additional people to test.
Don't look at me, I'll never touch an AOL CD!
AOL sucks so much I can't even describe it.
I use Avast on both of my home comps, and I would use it on the work box except we have licenses for Symantec Corporate... doesn't seem to get in the way of anything.
Guys I know AOL sucks, so I don't need you to indicate that here.
If you can't help me I would appreciate if you simply dont post at all.
This is for an issue with clients computers, not my own. I don't use AOL either.
Suggest that they get a real ISP and browser, informing them of every known reason why AOL sucks. My guess is they'll get the point about three hours into the list...
Unfortunately that's not how it works in the real world.Quote:
Originally Posted by timeshifter
We've pulled it off a few times.. made some money doing it, too.
Well I remember the McAffee Online Virusscan (I don't know if that comes with AOL) gave me grief. I had to boot up in safe mode to get rid of the damn thing.
And that's probably as helpful as I can get. Sorry.
We've had some very strange problems with McAfee and VS 2005 (and VS 2003 as well).Quote:
Originally Posted by kleinma
Unfortunately, the problems are as vague and countless as Bushisms. What is your specific problem?
The problem is that when prompted by the firewall to allow or deny access through the firewall, if you select deny it makes the framework crash my program (no exception thrown, just crash).Quote:
Originally Posted by mendhak
The behavior also happens if you are using the application framework and select your app to be a single instance application. This is because the underlying framework uses a tcpchannel (i think its tcp) to communicate between instances of your app.
Comodo firewall also causes the crash. Onecare firewall doesn't. I am looking to test a few others maybe. The McAfee Firewall that I was able to test is the free AOL one.
Treatments for AOL are given higher priority than cancer patients in the UK.
Actually if found McAffee causes alot of problems with alot of software.
Yours certainly wouldn't be the only software that crashes. World of warcraft crashes whenever any firewall software asks if you would like to block or allow the software to access the internet.Quote:
Originally Posted by kleinma
Haven't had that problem, you're on your own. I've had to specify that the firewall should ignore aspnet_wp.exe completely on a few machines.Quote:
Originally Posted by kleinma
In my experience mcaffee caused many adverse affects with many windows common controls (comboboxes being empty and so forth) too.
The issue also happens with Comodo Personal Firewall, so I can't really blame McAfee on this. I submitted this as a bug to MS in connect, and hopefully they can repro it and maybe provide a work around. It isn't a huge issue, but if I can't handle the exception gracefully in my app, then I am stuck being able to do nothing.
I suspect that the way that the firewall denies access may be at the root of the problem. I'd imagine that it somehow triggers an error in the calling application - but I'm afraid I don't know the details...
Is any error being written to the event log or can you attach a debugger (WinDbg) to see something happening?
Also - does it crash out when debugging in the IDE? or only in compiled app?
only when compiled (although doesn't matter if its debug or release)
But yes only when I ran the exe outside the IDE could I get this to happen.
I assume that has to do with the way VS hooks into an exe for debugging, and perhaps its the vshost that already has the needed firewall permissions, so you don't even get asked.
I can see what is happening, the DoBind method for the socket class fails (states invalid parameter), and a socketexception is thrown, just not one I am able to catch.Quote:
Originally Posted by Merrion