"Phantom" Warning Messages

  • Thread starter Thread starter Chuck Cobb
  • Start date Start date
C

Chuck Cobb

I'm doing a CSharp project in VS2005 and I'm getting some strange warning
messages. The problem is that the warning messages don't link to anything
in my code so they are very difficult to track down. Some of these also
seem to be "phantoms" where I think I've corrected the problem but the
warning message persists.

For example, I made some changes in my code and started getting a warning
message that I had a "duplicate component name" in a control - I was having
trouble tracking down this error, so I undid all the changes I had done to
get back to a clean slate and the warning messages won't go away after I
undid all the changes that might have caused the warning messages.

Has anyone seen this problem??? Is there a solution to it?

Thanks,

Chuck Cobb
 
I found a solution to this problem. Unloading the project from the solution
and reloading it made these "phantom" warning messages go away. I couldn't
do it any way I tried completely rebooting my system and that had no effect.

Is this a known VS2005 bug??

Chuck
 
This problem has come back again and its getting really annoying...it seems
to happen any time I make a major change to my project.

I recently upgraded my Infragistics controls from 5.3 to 6.1 and used the
Infragisitics project upgrade utility to replace all references to 5.3 with
6.1.

It was working fine for a while and I made another change that had nothing
to do with the Infragistics controls. Now all of a sudden, I'm getting (8)
warning messages saying "Unable to publish properties for
Infragisticsxxxx.v5.3". When I click on this warning message it goes no
where. I've done an extensive search for Infragistics 5.3 references and
can find none. I have no idea where these warnings are coming from and I've
wasted about an hour or two trying to track down their source with no
success.

Unloading and reloading the project doesn't remove them.

Any ideas or help would be much appreciated....

Thanks,

Chuck Cobb
 
I don't know about this particular situation, but in VS2003 I have run
across circumstances in which the WinForms Designer gets "stuck"
issuing bogus error messages. Closing the relevant designer windows,
rebuilding any DLLs on which the project depends, then rebuilding the
project itself clears mine up.

The problem seems to be that the Designer needs to instantiate an
object of a form's base class in order to let you design the form. If
the base class is in another project, then the Designer can get itself
"out of synch" and--seemingly--be stuck with an object created from a
stale version of the base class's library.

Closing all Designer windows seems to unload the Designer, or
something, and then a rebuild fixes things up. Opening a Designer
window again then works fine.

As I said, this is VS2003, and my experience isn't exactly like yours
because I don't use Infragistics controls.
 
Back
Top