help with VB solution

My harddrive crashed and I had rebuild and pull code from a backup server.  

I have a project that uses 2 DLL's.   I have the 2 DLL projects added into my solution.  I'm getting an error when running, but I cannot step into the code to debug.  The code getting the error is in the DLL source code.   I do not understand why I cannot step into it. This used to work,.

 See images.
error.png
error1.png
LVL 1
HLRosenbergerAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Jacques Bourgeois (James Burger)Connect With a Mentor PresidentCommented:
In the options, you have the "Step over properties and operators" option checked, so the debugger goes over these without entering them.

This is often set through a dialog that shows up the first time you encounter a call to a property while stepping through code after installing Visual Studio. The message might be confusing or annoying when your mind is focused on what is happening in the code, and many programmers close it without knowing about the consequences of their answer.
0
 
Jacques Bourgeois (James Burger)PresidentCommented:
You probably set the reference to the dlls instead of the project.

When you want to be able to step into a dll code, you need to set the reference differently, at least in VB and C#. I suppose this is the same thing in C++.

When you set the reference, you probably have a tab that list references to Projects instead of .NET or COM. This is were you should set your reference.
0
 
HLRosenbergerAuthor Commented:
but I'm adding each project to the main solution.  It that not the way to go?
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
HLRosenbergerAuthor Commented:
so, so I have add each project to the main solution, and then add as a "Project" type reference?
0
 
HLRosenbergerAuthor Commented:
uggg.    I have added each project to the main solution, and then added each as a "Project" type reference.  Still no go...
0
 
Jacques Bourgeois (James Burger)PresidentCommented:
Are you in VB or C++?

Is the debugger enabled for the configuration that you are using? As far as VB is concerned, if you installed a newer version of Visual Studio when you rebuilt your computer, there has been a small change for debugging. Some of the debugger features do not work anymore if you set the "Generate debug info" selection to pdb-Only in the Advanced Compile Options. It has to be set to Full.

Tools...Options...Debugging also has one or two options that can prevent stepping into your own properties and methods.

Can you send a screen shot of your Solution Explorer and one of your References?
0
 
HLRosenbergerAuthor Commented:
same version of VS as before - 2010.  See images.

I have added the 2 DLL projects into my solution, and then added the projects as a reference.

I still cannot step inte the DLL source code.
image1.png
image2.png
image3.png
image4.png
0
 
HLRosenbergerAuthor Commented:
That was it. Thanks!   In my old setup before the harddrive crashed, this must have not been checked.
0
All Courses

From novice to tech pro — start learning today.