By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,671 Members | 1,559 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,671 IT Pros & Developers. It's quick & easy.

dll problem

P: n/a
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
Nov 15 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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" <ri**@abasoftware.com> wrote in message
news:#Q**************@TK2MSFTNGP10.phx.gbl...
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

Nov 15 '05 #2

P: n/a
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
"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
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" <ri**@abasoftware.com> wrote in message
news:#Q**************@TK2MSFTNGP10.phx.gbl...
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


Nov 15 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.