Debugging a Dll used by an application

I have an application that uses a dll.  They are both in the same solution.  I am having a problem setting break points inside the dll and debugging it.  Thanks guys.  I've seen some of the documentation but still hitting a wall.  Thanks.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

1. ensure that both projects are built in debug mode, and both are build with compatible options (Debug MT is incompatible with Debug MT DLL)
2. mark the DLL project as a startup project
3. set executable name (Debugging/Command) for DLL project from EXE project
4. set breakpoints in DLL project
5. run

Where do you get problems?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
graberAuthor Commented:
I have to do this from the exe side.  There are configuration files located in that directory that won't be seen from the dll side.
graberAuthor Commented:
Actually that will work.  There are only 3 files that I need. I'll just copy them into the start up folder.  Thanks.  But could you tell me who to do the same thing from the exe side?
Become a Certified Penetration Testing Engineer

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

graberAuthor Commented:
The application launches like it should but the break points are not setting.
You can tell in the Debugging what's the start directory for the DLL.
Again: the startup project is of the DLL, not the EXE.
I seem to recall having this problem at one point, and solved it by breakpointing early in the EXE.  As soon as the EXE was in debug mode, I could then breaakpoint the DLL (and/or single-step into it).

But it shouldn't be necessary to do it that way... if the DLL is marked as a dependancy of the EXE, VS should accept breakpoints in it.
graberAuthor Commented:
Set the Debug option "Debug Type" to mixed for both projects and vowala.
graberAuthor Commented:
this will work but it wasn't the cleanest.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Editors IDEs

From novice to tech pro — start learning today.