Re: Debugging main app with compiled DLL
- From: kimiraikkonen <kimiraikkonen85@xxxxxxxxx>
- Date: Fri, 21 Mar 2008 02:45:33 -0700 (PDT)
On Mar 21, 11:30 am, "Gareth" <batty...@xxxxxxxxx> wrote:
Hi,
I am debugging a new VB.net app using INI functions from a pre compiled .NET
dll.
When I come to a line calling a function in the DLL, the debugger knows
where the code of the dll is and shows it when I use F8 to proceed to the
next line of code.
I have copied the compiled DLL to the debug folder of the main app and used
the 'reference' screen to 'point' to that dll, but it still shows me the dll
code.
Can anyone tell me how to switch this off because I will be making many many
classes with DLLs and I really don't want the vb.net debugger to take me
constantly to already well debugged code of the compiled DLL.
Thanking you in advance
Garry
If your DLL is compiled, just reference it, through your project in
solution explorer -> right click -> add reference -> browse.
Don't add the DLL to your project by file -> add -> new project ->
class library. When you reference just the compiled DLL under your
project you'll be able to use and call the libraries and no source
code of the DLL will be shown on your VS IDE.
.
- References:
- Debugging main app with compiled DLL
- From: Gareth
- Debugging main app with compiled DLL
- Prev by Date: Re: ComboBox drop-down window closing/hidden
- Next by Date: VB2005 Microsoft.printform 1.0 Component
- Previous by thread: Debugging main app with compiled DLL
- Next by thread: Re: Debugging main app with compiled DLL
- Index(es):
Relevant Pages
|
