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

How to debug(step thru) a main appl with 33 projects in it?

P: n/a
Hi, I'm fixing a bug in an application and need to step thru the appl to find
where it's occuring. The main project includs 33 other projects each having
a .resx file in it. When I step through it would give me message that it
can't show me codes because only assembly codes are available.

Is there any good article on how to debug something like this? Also, I've
only being working with C#.net for 3 months and am still not very familiar on
using the debug and compile setting. Can someone also tell me a good article
to read up on this? I looked up some C# books but they're all very
fundamental and not very detial and helpful.

Thanks, Alpha
Nov 17 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
I am a little confused from what you are saying so I will ask some
questions:

Are you attempting to debug a 'Release' or 'Debug' build? - make sure it is
a debug build

If you know approximately where the problem is occuring then place you could
use a 'Debugger.Break' statement - this will allow you to atttach a
debutgger to the code and step through the code. Check out the following
link for usage

http://msdn.microsoft.com/library/de...BreakTopic.asp

Infact check out the System.Diagnostics namespace it has lots of use
classes, including classes that allow you to trace information into the
VS.Net IDE at runtime (System.Diagnostics.Trace)
--
HTH

Ollie Riches
http://www.phoneanalyser.net
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a programmer
helping programmers.

"Alpha" <Al***@discussions.microsoft.com> wrote in message
news:9C**********************************@microsof t.com...
Hi, I'm fixing a bug in an application and need to step thru the appl to
find
where it's occuring. The main project includs 33 other projects each
having
a .resx file in it. When I step through it would give me message that it
can't show me codes because only assembly codes are available.

Is there any good article on how to debug something like this? Also, I've
only being working with C#.net for 3 months and am still not very familiar
on
using the debug and compile setting. Can someone also tell me a good
article
to read up on this? I looked up some C# books but they're all very
fundamental and not very detial and helpful.

Thanks, Alpha

Nov 17 '05 #2

P: n/a
I open the main appl in VS.net 2003. I want to run the application in the
debug mode to find the module or project where the bug is occuring so I can
fix it. I click the play arrow to run the appl in the debug mode and select
the Break-All under Debug menu when I get the problem area of the appl to
find out which Module it is. But it's here that I'm getting the message that
only assembly is avaiable.

In the project area of the main appl there are 33 other projects folder and
when expanded there is only .resx file. I think that's why I can't debug.
Can you point me to certain web page where I can find more information about
setting the debug and build options? Thanks.

"Ollie Riches" wrote:
I am a little confused from what you are saying so I will ask some
questions:

Are you attempting to debug a 'Release' or 'Debug' build? - make sure it is
a debug build

If you know approximately where the problem is occuring then place you could
use a 'Debugger.Break' statement - this will allow you to atttach a
debutgger to the code and step through the code. Check out the following
link for usage

http://msdn.microsoft.com/library/de...BreakTopic.asp

Infact check out the System.Diagnostics namespace it has lots of use
classes, including classes that allow you to trace information into the
VS.Net IDE at runtime (System.Diagnostics.Trace)
--
HTH

Ollie Riches
http://www.phoneanalyser.net
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a programmer
helping programmers.

"Alpha" <Al***@discussions.microsoft.com> wrote in message
news:9C**********************************@microsof t.com...
Hi, I'm fixing a bug in an application and need to step thru the appl to
find
where it's occuring. The main project includs 33 other projects each
having
a .resx file in it. When I step through it would give me message that it
can't show me codes because only assembly codes are available.

Is there any good article on how to debug something like this? Also, I've
only being working with C#.net for 3 months and am still not very familiar
on
using the debug and compile setting. Can someone also tell me a good
article
to read up on this? I looked up some C# books but they're all very
fundamental and not very detial and helpful.

Thanks, Alpha


Nov 17 '05 #3

P: n/a
"Alpha" <Al***@discussions.microsoft.com> wrote in message
news:68**********************************@microsof t.com...
I open the main appl in VS.net 2003. I want to run the application in the
debug mode to find the module or project where the bug is occuring so I
can
fix it. I click the play arrow to run the appl in the debug mode and
select
the Break-All under Debug menu when I get the problem area of the appl to
find out which Module it is. But it's here that I'm getting the message
that
only assembly is avaiable.

In the project area of the main appl there are 33 other projects folder
and
when expanded there is only .resx file. I think that's why I can't debug.
Can you point me to certain web page where I can find more information
about
setting the debug and build options? Thanks.


You shouldn't have to set any particular options - (what are your other type
of apps? Also C#?) When you break the app, close the warning about only
assembly being available and look at the Call Stack window. That should
tell you where in your code you are.

--
Adam Clauss
Nov 17 '05 #4

P: n/a
Yes most are in C# of the 33 projects except for 2 of them.

OK. thanks. I think that will tell me which project/module. But what if I
want to step through that project /module? It doesn't work now.

"Adam Clauss" wrote:
"Alpha" <Al***@discussions.microsoft.com> wrote in message
news:68**********************************@microsof t.com...
I open the main appl in VS.net 2003. I want to run the application in the
debug mode to find the module or project where the bug is occuring so I
can
fix it. I click the play arrow to run the appl in the debug mode and
select
the Break-All under Debug menu when I get the problem area of the appl to
find out which Module it is. But it's here that I'm getting the message
that
only assembly is avaiable.

In the project area of the main appl there are 33 other projects folder
and
when expanded there is only .resx file. I think that's why I can't debug.
Can you point me to certain web page where I can find more information
about
setting the debug and build options? Thanks.


You shouldn't have to set any particular options - (what are your other type
of apps? Also C#?) When you break the app, close the warning about only
assembly being available and look at the Call Stack window. That should
tell you where in your code you are.

--
Adam Clauss

Nov 17 '05 #5

P: n/a
"Alpha" <Al***@discussions.microsoft.com> wrote in message
news:97**********************************@microsof t.com...
Yes most are in C# of the 33 projects except for 2 of them.

OK. thanks. I think that will tell me which project/module. But what if
I
want to step through that project /module? It doesn't work now.


That will tell you nto only process/module, but exactly which functions are
being called.
If you are getting assembly, then you are likely making some System call
that really won't help you much anyway. There should be a command to
"Step-Out" that will take it up one level at a time in the call stack. As
soon as you get to your code again, you can see where it is and set
breakpoints, step through, do whatever it is you need to do.
--
Adam Clauss
Nov 17 '05 #6

P: n/a
I will try that. Thank you.

"Adam Clauss" wrote:
"Alpha" <Al***@discussions.microsoft.com> wrote in message
news:97**********************************@microsof t.com...
Yes most are in C# of the 33 projects except for 2 of them.

OK. thanks. I think that will tell me which project/module. But what if
I
want to step through that project /module? It doesn't work now.


That will tell you nto only process/module, but exactly which functions are
being called.
If you are getting assembly, then you are likely making some System call
that really won't help you much anyway. There should be a command to
"Step-Out" that will take it up one level at a time in the call stack. As
soon as you get to your code again, you can see where it is and set
breakpoints, step through, do whatever it is you need to do.
--
Adam Clauss

Nov 17 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.