471,627 Members | 1,590 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,627 software developers and data experts.

Can't step into?

I have referenced two .NET DLLs in my project. When debugging, I step
into one of aDLL's methods. aDLL inherits from bDLL. In aDLL, there
is a method called from bDLL. However, I cannot step into it. For
example:
[Project.class1] ( start debugging here and step into mya.dosomething)
aDLL.someclass mya = new aDLL.someclass();
mya.dosomething()

[aDLL.someclass:bDLL.anotherclass] (I can get here with no problems. I
cannot step into getResults)
myObject mo = new myObject();
public void something()
{
mo = getResults()
}

[bDLL.anotherclass] (Can't get here in debugger)
public void getResults()
{
--do something here
}

Why can I get into aDLL but not bDLL?

Thanks,
Brett

Dec 29 '05 #1
5 2566
Brett Romero wrote:
I have referenced two .NET DLLs in my project. When debugging, I step
into one of aDLL's methods. aDLL inherits from bDLL. In aDLL, there
is a method called from bDLL. However, I cannot step into it. For
example:
[Project.class1] ( start debugging here and step into mya.dosomething)
aDLL.someclass mya = new aDLL.someclass();
mya.dosomething()

[aDLL.someclass:bDLL.anotherclass] (I can get here with no problems. I
cannot step into getResults)
myObject mo = new myObject();
public void something()
{
mo = getResults()
}

[bDLL.anotherclass] (Can't get here in debugger)
public void getResults()
{
--do something here
}

Why can I get into aDLL but not bDLL?

Thanks,
Brett


Hi Brett,

A few ideas:

Are you properly using inheritance?
-are bDLL's methods virtual?
-Are you overriding the method?
-Are you calling base.method where you want to execute the base classes
methods

It also may be possible that your symbols aren't looking at the right
assembly. Do you have a project reference correctly set, and is your
assembly in the GAC or someplace else?
--
Rob Schieber
Dec 29 '05 #2
>Are you properly using inheritance?
I'm not getting any errors and the base method is executing (that I
know of). What else could say I'm not using inheritance correctly?
-are bDLL's methods virtual? Not the one I'm calling. It is public.
-Are you overriding the method? No. I'm calling it from the base. In the base, it is simply a public
string method.
-Are you calling base.method where you want to execute the base classes

methods
I have done "this.", "base." and just the method name. Same results in
each case.

Thanks,
Brett

Dec 29 '05 #3
Brett Romero wrote:
Are you properly using inheritance?


I'm not getting any errors and the base method is executing (that I
know of). What else could say I'm not using inheritance correctly?

-are bDLL's methods virtual?


Not the one I'm calling. It is public.

-Are you overriding the method?


No. I'm calling it from the base. In the base, it is simply a public
string method.

-Are you calling base.method where you want to execute the base classes


methods
I have done "this.", "base." and just the method name. Same results in
each case.

Thanks,
Brett


If you are positive that the base method is executing correctly, then it
is probably a reference issue. Make sure that you have your project
references set up correctly. You may want to remove and re-add your
references just to be sure. Also, make sure everything is compiled in
debug mode.
--
Rob Scheiber
Dec 29 '05 #4
BTW, these aren't in the GAC. They are in their respective project bin
folders and then copied to the referencing project's bin.

I tried your suggestion of rebuilding the referenced DLL then
removing/adding it back to my project. That worked! Great suggestion.
The DLL was also doing incremental versioning, which I turned off.
The versions are now hard coded. I don't need versioning issues at
this point.

Thanks,
Brett

Dec 29 '05 #5
If you have the projects to both .dll's it is better in the referencing
project to *not* reference the .dll's directly. It is better to add
the projects to your solution and use project referencing instead.
That should alleviate the versioning and debugging issues you are
having.

Dec 30 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Andrew V. Romero | last post: by
3 posts views Thread by R Millman | last post: by
4 posts views Thread by MichaelCombs | last post: by
3 posts views Thread by =?Utf-8?B?QWxleCBNYWdoZW4=?= | last post: by
1 post views Thread by XIAOLAOHU | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.