|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Stepping into a referenced assemblycan 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 Has gToc been compiled in release mode? You cant step into release compiled
code. Ooooh if only you could...but you cant. But oooohh if only you could. Richard Show quoteHide quote "Steve Long" <Steve_Noneya@NoSpam.com> wrote in message news:e62hX3GQFHA.3076@TK2MSFTNGP14.phx.gbl... > 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 > > Make sure youre using the debug versions of the assemblies, load one of the
source files from the assembly and put a breakpoint where you want it. You should also read the article in Windows Forms Tips and Tricks that shows how to debug a component. The technique for debugging into ordinary assemblies is identical. -- Show quoteHide quoteBob Powell [MVP] Visual C#, System.Drawing Find great Windows Forms articles in Windows Forms Tips and Tricks http://www.bobpowell.net/tipstricks.htm Answer those GDI+ questions with the GDI+ FAQ http://www.bobpowell.net/faqmain.htm All new articles provide code in C# and VB.NET. Subscribe to the RSS feeds provided and never miss a new article. "Steve Long" <Steve_Noneya@NoSpam.com> wrote in message news:e62hX3GQFHA.3076@TK2MSFTNGP14.phx.gbl... > 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 > > Thanks Richard and Bob. For some reason, a release version must have gotten
in there. And they said the end to DLL Hell. Ha. But, that did the trick. Much appreciated. Show quoteHide quote "Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message news:Okjh1%23GQFHA.904@tk2msftngp13.phx.gbl... > Make sure youre using the debug versions of the assemblies, load one of the > source files from the assembly and put a breakpoint where you want it. > > You should also read the article in Windows Forms Tips and Tricks that shows > how to debug a component. The technique for debugging into ordinary > assemblies is identical. > > -- > Bob Powell [MVP] > Visual C#, System.Drawing > > Find great Windows Forms articles in Windows Forms Tips and Tricks > http://www.bobpowell.net/tipstricks.htm > > Answer those GDI+ questions with the GDI+ FAQ > http://www.bobpowell.net/faqmain.htm > > All new articles provide code in C# and VB.NET. > Subscribe to the RSS feeds provided and never miss a new article. > > > > > > "Steve Long" <Steve_Noneya@NoSpam.com> wrote in message > news:e62hX3GQFHA.3076@TK2MSFTNGP14.phx.gbl... > > 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 > > > > > > |
|||||||||||||||||||||||