S
Samuel R. Neff
Within the past few weeks we've been getting a lot of compiler errors
in two classes when no errors actually exist. The error always
reports as
Name '_stepResizeRelocator' is not declared.
Where _stepResizeRelocator is an instance (class level) variable.
There is no compiler error on the declaration of the variable, only on
use. Tthe name of the variable which causes the error changes.
If we choose "Rebuild Solution" then the errors go away, but when we
choose "Build Solution" or "Start" the compiler errors are present.
We can fix the errors by closing VS.NET and deleting the vbc*.tmp
files.
Any suggestions on what can be causing these errors and how we can
correct them (without having to close vs.net and delete temp files
manually)?
We're using VS.NET 2003 and VB.NET WinForms. The solution has seven
projects in it all controlled through VSS. 4 person team. We all get
the same type of errors with same work-around and are all running XP
Pro.
We only have this problem in two files (one extends the other) which
is one of the DLL's and is a user control.
We're using Infragistics controls and one of my co-workers thinks that
may be related, but we don't have the problem in other classes that
use Infragistics controls (however, these classes are the only ones
that use their Grid).
Thanks,
Sam
B-Line is now hiring one Washington D.C. area VB.NET
developer for WinForms + WebServices position.
Seaking mid to senior level developer. For
information or to apply e-mail resume to
sam_blinex_com.
in two classes when no errors actually exist. The error always
reports as
Name '_stepResizeRelocator' is not declared.
Where _stepResizeRelocator is an instance (class level) variable.
There is no compiler error on the declaration of the variable, only on
use. Tthe name of the variable which causes the error changes.
If we choose "Rebuild Solution" then the errors go away, but when we
choose "Build Solution" or "Start" the compiler errors are present.
We can fix the errors by closing VS.NET and deleting the vbc*.tmp
files.
Any suggestions on what can be causing these errors and how we can
correct them (without having to close vs.net and delete temp files
manually)?
We're using VS.NET 2003 and VB.NET WinForms. The solution has seven
projects in it all controlled through VSS. 4 person team. We all get
the same type of errors with same work-around and are all running XP
Pro.
We only have this problem in two files (one extends the other) which
is one of the DLL's and is a user control.
We're using Infragistics controls and one of my co-workers thinks that
may be related, but we don't have the problem in other classes that
use Infragistics controls (however, these classes are the only ones
that use their Grid).
Thanks,
Sam
B-Line is now hiring one Washington D.C. area VB.NET
developer for WinForms + WebServices position.
Seaking mid to senior level developer. For
information or to apply e-mail resume to
sam_blinex_com.