By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,156 Members | 1,004 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,156 IT Pros & Developers. It's quick & easy.

Debugger Type == Auto isn't smart for DLL projects

P: n/a
VS.NET 2003 defaults the "Debugger Type" property to "Auto" for Visual C++
projects. Unfortunately, the "Auto" type isn't very smart. "Auto" bases
the debugger type on the launched EXE's type, which may have nothing to do
with the C++ project I'm trying to debug.

I have a .NET EXE that hosts all of my DLLs, but a lot of the DLLs are old,
unmanaged C++ COM DLLs. Now everytime I debug one of them, I have to
remember to change the debugger type to "Native Only".

"Auto" should be based on the startup project's build settings. If it is an
EXE build, then use the current "Auto" behavior. But if it is a DLL build,

* If it is an unmanaged C++ project (i.e., it is NOT using managed
extensions), then the debugger type should be native only.

* If it is a purely managed C++ project, then the debugger type should
be managed.

* If it is a mixed-mode project, then the debugger type should be mixed.

The type of EXE you're launching isn't relevant to the debugger type needed
for a C++ DLL. My assumption here is that if I choose a C++ DLL project as
the startup project when debugging, then I want to debug in the mode most
appropriate for that project's settings and NOT a mode based on the EXE
that's hosting the DLL.

I'm also tired of answering the "Why isn't it hitting any of my
breakpoints?" question for co-workers because they forget or don't know
about the "Debugger Type" property.

Is there any chance this is fixed/changed in VS.NET 2005?
Nov 17 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Hi Bill,

You suggestion is very valuable, you may submit a wish to out mswish
website. Our product team will review and evaluate the feedback.

Microsoft offers several ways for you to send comments or suggestions about
Microsoft products. If you have suggestions for product enhancements that
you would like to see in future versions of Microsoft products, please
contact us using one of the methods listed later in this article.

Let us know how we can improve our products.

Product Enhancement suggestions can include:

" Improvements on existing products.
" Suggestions for additional features.
" Ways to make products easier to use.

World Wide Web - To send a comment or suggestion via the Web, use one of
the following methods:

" In Internet Explorer 6, click Send Feedback on the Help menu and then
click the link in the Product Suggestion section of the page that appears.
" In Windows XP, click Help and Support on the Start menu. Click Send your
feedback to Microsoft, and then fill out the Product Suggestion page that
" Visit the following Microsoft Web site:
" Click Guide in the upper-right corner of the page and then
click Contact Us . Click the link in the Product Suggestion section of the
page that appears.
" Visit the following Microsoft Product Feedback Web site:
"" and then complete and
submit the form.

E-mail - To send comments or suggestions via e-mail, use the following
Microsoft Wish Program e-mail address, ms****
FAX - To send comments or suggestions via FAX, use the following Microsoft
FAX number, (425) 936-7329.

Each product suggestion is read by a member of our product feedback team,
classified for easy access, and routed to the product or service team to
drive Microsoft product and/or service improvements. Because we receive an
abundance of suggestions (over 69,000 suggestions a year!) we can't
guarantee that each request makes it into a final product or service. But
we can tell you that each suggestion has been received and is being
reviewed by the team that is most capable of addressing it.

All product or service suggestions received become the sole property of
Microsoft. Should a suggestion be implemented, Microsoft is under no
obligation to provide compensation.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! -
This posting is provided "AS IS" with no warranties, and confers no rights.

Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.