Dubugger goes to code of .net DLL

[Gareth]

Hi,

I have a new VB.NET project and a VB.NET dll.

The DLL is compiled directly to the bin\debug folder of the VB.NET project

The project reference path for the DLL is to the compiled DLL in the
bin\debug folder. (not the bin\debug folder of the DLL code project)

BUT, when I get to code referencing the DLL functions in the main VB.NET
project, the debugger goes to the code of the DLL. (How it knows where the
code is - I have no idea).

This is not what I want as the DLL functions are well debugged.

I have looked for some parameter to control this 'affliction' and have found
no solution.

Anyone any ideas????

Thanking them in advance.

Garry

 

[Rory Becker]

Hello Gareth,

BUT, when I get to code referencing the DLL functions in the main
VB.NET project, the debugger goes to the code of the DLL. (How it
knows where the code is - I have no idea).

This is not what I want as the DLL functions are well debugged.

F10 can be used to step over (execute without steping into the code)
F11 only for stepping in.
Shift F11 can be used to complete a procedure if you accidentally step into
it.

Hope this helps

 

[Gareth]

Yes.

Thank you Rory.

I 'came from' VB6 and thought that I 'knew it all'.

Thanks again.

Garry

 

[Anthony Jones]

Hi,

I have a new VB.NET project and a VB.NET dll.

The DLL is compiled directly to the bin\debug folder of the VB.NET project

The project reference path for the DLL is to the compiled DLL in the
bin\debug folder. (not the bin\debug folder of the DLL code project)

BUT, when I get to code referencing the DLL functions in the main VB.NET
project, the debugger goes to the code of the DLL. (How it knows where the
code is - I have no idea).

This is not what I want as the DLL functions are well debugged.

I have looked for some parameter to control this 'affliction' and have found
no solution.

Anyone any ideas????

Build a release version of the dll and reference that.

 

[Gareth]

Great idea Anthony Jones.

I'll try that too since I amused to F8. My hand seems to take me to F8
automatically.

Garry

 

[Gareth]

Anthony Hi,

I looked in the various parameters available for the DLL and cannot see one
for 'a release version of the dll'

Before I used menu Build/Build <DLLName>



Any more help????

Garry

 

[Anthony Jones]

Anthony Hi,

I looked in the various parameters available for the DLL and cannot see one
for 'a release version of the dll'

Before I used menu Build/Build <DLLName>



Any more help????

Do you have your project and your dll project in the same solution?

The standard tool bar will have a drop down containing existing
configurations typiclaly Debug and Release. Change it to release and build
your DLL project. Remove the project from your solution and change the
reference to is in the project you are debugging to the dlls bin\release
folder.

Personally I wouldn't bother and simply use Step Into, Step Over and Step
Out as appropriate its not like you'll not be doing that for code within a
project anyway.

 

[Rory Becker]

Hello Gareth,

Yes.

Thank you Rory.

I 'came from' VB6 and thought that I 'knew it all'.

Nothing wrong with Vb6. Just please don't ever make me go back there

Worth noting that the keys I mentioned might change dependant on the keboard
scheme you have in place, but the commands ( step in /out/over) should be
on the Debug menu

 

[Gareth]

Thanks Rory.

The scheme fits fine.

garry

Hello Gareth,


Nothing wrong with Vb6. Just please don't ever make me go back there

Worth noting that the keys I mentioned might change dependant on the
keboard scheme you have in place, but the commands ( step in /out/over)
should be on the Debug menu

 

[Gareth]

Antony Hi,

"The standard tool bar will have a drop down containing existing
configurations typiclaly Debug and Release. "

As far as I know, I have the 'standard' toolbar visible and there is no
dropdown/combo control on it. I did try displaying different tool bars
including the 'debug' and 'build' toolbars but nothing helped me there.

Anyway, F10, F11 and Shift/F11 being extremly useful.

Incidentally, I 'asked' the vs.2008 help for "keyboard shortcuts in VB.net"
and recieved a literal sunami of usless and unconnected articles.

When will Microsoft learn from Google.

Thank you for your time.