The normal way is to temporarily include the other source project in the
solution when you debug. You can remove the project later.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************************************************
Think outside the box!
*************************************************
"billg_sd" <bi******@discussions.microsoft.com> wrote in message
news:6D**********************************@microsof t.com...
I'm debugging a VB.NET Windows Form app. I've included .NET DLL from a
different project (that I have access to). I need to be able to jump into
this other Dll's Source code while debugging.
When I attempt to step into the source code, I receive the message "There
is no source code available for the current location."
I'm given NO option to browse/identify the vb file. And I don't How can I
do this?