dll problem

[RickN]

My C# solution contains multiple projects. It references the business logic
solution which also contains multiple projects.

I have two strange (and probably related) problems.

1) The first application is throwing an error saying the referenced project
doesn't contain (a newly added) method. However, it does. When I debug it,
I examine the referenced dll and it clearly does contain the method.

2) When stepping through the debug process for another error, the debugger
is stepping through //marked out code as if it wasn't marked out.

Any suggestions as to what would be causing this strange behaviour.

Thanks,
Rick

 

[Rob Teixeira [MVP]]

When one project references another project, the referneced project gets
built first, then the output DLL is copied (by default) to the bin directory
of the second project.
Sounds to me like they aren't in sink.
Delete the bin folders and re-add the reference just to be on the safe side.
The weird debugger stepping issues usally happen if the PDB file isn't in
sync with the DLL or EXE.

-Rob [MVP]

 

[RickN]

Thanks, I'll try that.
In the process, I noticed that some of the other project references were to
the \referencing solution\project\obj\debug folder while others were to the
\referencing solution\project\bin\debug folder. What's the difference and
when browsing to add a reference, where should the reference be pointing.

Thanks,
Rick