Bug in .Net or.......

  • Thread starter Thread starter Erik
  • Start date Start date
E

Erik

Hi there,

I've recently bought a new laptop (Dell Latitude D800) for software
designing/building purposes, and i've installed a fresh VS2003 with
framework 1.1 SP1 on it. But I've been experience some strange
behaviour of my .Net applications:

- Transparent icons are only transparent in design-time. Run-time they
get the maskcolor as background color
- Listbox control doesn't show any item, although the items are
present in the control (can click on the items, but you just don't see
any text). The checkedListBox works fine.

Applications build (with a listbox on it) on my Dell work fine on
other machines...

And'I've got that feeling that this is not the only strange behaviour
to expect...

I've haven't got any clue. I've re-installed the .Net framework
several times, with no effect. Probably it has something to do with my
graphics card? Strange thing is that it all works fine in design-time
(in VS), but runtime it fails to work properly....

Anybody any clue?

Greetz,
Tsjap.
 
Erik said:
Hi there,

I've recently bought a new laptop (Dell Latitude D800) for software
designing/building purposes, and i've installed a fresh VS2003 with
framework 1.1 SP1 on it. But I've been experience some strange
behaviour of my .Net applications:

- Transparent icons are only transparent in design-time. Run-time they
get the maskcolor as background color
- Listbox control doesn't show any item, although the items are
present in the control (can click on the items, but you just don't see
any text). The checkedListBox works fine.

Applications build (with a listbox on it) on my Dell work fine on
other machines...

And'I've got that feeling that this is not the only strange behaviour
to expect...

I've haven't got any clue. I've re-installed the .Net framework
several times, with no effect. Probably it has something to do with my
graphics card? Strange thing is that it all works fine in design-time
(in VS), but runtime it fails to work properly....

Anybody any clue?

Greetz,
Tsjap.
Click to expand...

Using MacAfee antivirus? There's a known incompatibility between McAfee and
VS 2003 for which McAfee issued a patch. If you don't use McAfee, check
other software running on your new laptop and turn things off until you find
the culprit.
 
Peter van der Goes said:
Using MacAfee antivirus? There's a known incompatibility between McAfee and
VS 2003 for which McAfee issued a patch. If you don't use McAfee, check
other software running on your new laptop and turn things off until you find
the culprit.
Click to expand...

Yep. Running on McAfee 8.0i. Thanks for your answer. I've installed
the patch and it all works fine now...

What's puzzelin' me is how a virus scanner (a VIRUS SCANNER for crying
out loud!) is able to influence the behaviour of such components?

Greetz,
Tsjap
 
Erik said:
Yep. Running on McAfee 8.0i. Thanks for your answer. I've installed
the patch and it all works fine now...

What's puzzelin' me is how a virus scanner (a VIRUS SCANNER for crying
out loud!) is able to influence the behaviour of such components?

Greetz,
Tsjap
Click to expand...

Virus scanners are, by nature, very invasive. They have to be to detect "bad
guys". The interesting part of this is why did McAfee's code break the
display routines, where other similar products do not? That would be an
interesting question to pose to MacAfee ;)
As a user of AVG Anti-Virus (which has protected me well for two years and
never caused such issues), I'd suggest you investigate some competing
scanners.
 
Back
Top