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.

I have the same problem in a 2003 .net VB project that has about 30 classes.
F5 (run) gives compiler errors, Build gives the same, and Rebuild works fine.
One small edit change and the problem comes back. I think we have both
walked into the same MS bug wherein MS doesn't quite get all of the work done
in the right order in a build, but rebuild works fine. In these forums, I
asked for a way to tell the .net IDE to treat all builds as rebuilds - got no
response. My workaround is to do a lot of rebuilds which is not too painful
because my projects are smallish. My instincts tell me Infragistics is not
related to your problem. I believe it is entirely internal to MS
build/rebuild logic. I only have this problem in one project - the biggest
one.




"Samuel R. Neff" wrote:

>
> 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.
>

Hi Samuel,

Based on my test, it is hard to reproduce the problem.
Can you provide a reproduce project and send to by removing "online" from
my email?

So that we can try to reproduce the problem on my side and try to
troubleshooting the issue.

Also from your description, it seems that you have found a workaround while
you need to know the root cause and want a solution.
If so, I think you would better submit a Service Request to MSPSS which
will do dump analysis or live debugging on your machine so as to collection
enough information to troubleshooing the problem.

You may reach MSPSS via the link below.
http://support.microsoft.com

BTW: If we confirm this is an issue in our product, the support incident
fee will be refund.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.