Re: Stepping into a referenced assembly
- From: "Steve Long" <Steve_Noneya@xxxxxxxxxx>
- Date: Mon, 18 Apr 2005 09:01:38 -0700
I could have sworn I had posted this earlier but I don't see my post today
so I'll say thank you again to both Richard and Bob for responding to my
request. The solved my dumb little problem. For some reason, I guess the dll
had gotten compiled into a release mode so I fixed it and was good to go
again.
Steve
"Steve Long" <Steve_Noneya@xxxxxxxxxx> wrote in message
news:e62hX3GQFHA.3076@xxxxxxxxxxxxxxxxxxxxxxx
> Hello,
> can anybody tell me what the trick is to getting VB.NET 2003 to step into
> the code of an assembly that I have referenced in my project?
> For instance, I have these two assemblies, both written by me in VB.NET
> 2003, and both referenced in my project. I have some code that looks like
> the following:
>
> With g_toc
> .RefreshLegend = False
> .ShapePath = g_RegCtl.Reg.AvShapes
> .AvDataPath = g_RegCtl.Reg.AvData
> End With
>
> Both g_toc and g_RegCtl are instance variables created from the assemblies
> that I have reference and when I step through the code above, VB will load
> the class g_RegCtl.Reg into the debugger and step into AvShapes. Likewise
> for AvData, but it won't load the class for g_toc from that assembly so I
> can step into g_toc.ShapePath for instance.
> What gives????
>
> Thanks in advance for any smart ones out there that can shed light on this
> for me.
>
> Steve
>
>
.
- References:
- Stepping into a referenced assembly
- From: Steve Long
- Stepping into a referenced assembly
- Prev by Date: RE: VB6 to VB.Net Conversion
- Next by Date: Re: Delete Sheets in Excel
- Previous by thread: Re: Stepping into a referenced assembly
- Next by thread: run file remotely
- Index(es):
Relevant Pages
|