CLR Debugger points to incorrect source code

[Russ]

I have two programs with the same name but different name spaces.

i.e .

BusinessProcess.Provider
and
DataAccess.Provider


What happens when I debug remotely, is that the debugger will point to
the BusinessProcess.Provider instead of the DataAccess.Provider. I can
tell that its really executing DataAccess.Provider because of the line
numbers and the variables change values as if its executing
DataAccess.Provider. But, its still pointing to
BusinessProcess.Provider while debugging.

Anyone know how to make the CLR debugger point to the correct
namespace.program?

 

[Bryan Phillips]

If you are using .Net 1.1, be aware that this can also be caused by an
issue with incorrectly generated PDB files.

Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com

 

[Russ]

That was my first thought. But that is not the issue here.

Whats really weird, is that I will be in DataAccess.Provider and set a
break point, and it will pop over to BusinessProcess.Provider to set
the break point. And, that could be a empty line or even a commented
out line in BusinessProcess.Provider. When it runs it will stop on
that break point in the BusinessProcess.Provider but I can tell its
really running DataAccess.Provider.

 

[Ben Voigt]

That was my first thought. But that is not the issue here.

Whats really weird, is that I will be in DataAccess.Provider and set a
break point, and it will pop over to BusinessProcess.Provider to set
the break point. And, that could be a empty line or even a commented
out line in BusinessProcess.Provider. When it runs it will stop on
that break point in the BusinessProcess.Provider but I can tell its
really running DataAccess.Provider.

Are the filenames also the same (i.e. Provider.cs for both)?

Does it help if you supply the full path to the files when invoking the
compiler (csc)?

 

[Russ]

Yes the Filenames are the same.

In my example, they are

BusinessProcess.Provider.vb
DataAccess.Provider.vb

I only have this problem when debugging remotely using the CLR
debugger. I do not have any problems when using Visual Studio
debugging on my local machine.