S
Steve Long
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
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