Thanks Rag. From reading related documentation, I can see that debugger.break() would help in an executable/windows form project. However, since a class library project cannot be run within the context of the VB 2008 IDE (or so it seems), my original question remains.
Again, helpful instruction would be appreciated. On Jan 7, 12:37 pm, "Raghupathi Kamuni" <[email protected]> wrote: > Debugger.Break() > > > > On Tue, Jan 6, 2009 at 9:14 PM, Rob <[email protected]> wrote: > > > All, > > > I've just embarked on 2 web-application recoding projects which will > > be based on the following design: > > > Database: MS Access > > Application logic and DB interface: VB.Net Class Library (DLL) > > Presentation: Classic ASP > > > VB6 enables one to run a class library within the IDE allowing > > external clients (e.g. an ASP script or other executable) to access > > classes and associated functions through Server.CreateObject. Great > > during the development phase! VB6's breakpoints, immediate window, > > etc. all aid debugging. > > > However, I'm now struggling to see how to enable interactive debugging > > of a class library in VB.NET <http://vb.net/>. I wish to avoid recompiling > > the DLL with > > each incremental change to "test" implementation/functionality (and > > that blindly). I ask for help following 5-6 hours of googling without > > result. > > > If someone could give me a few pointers, I'd appreciate it. > > > Thanks in advance, > > > Rob. > > > N.B. Due to project constraints, I should emphasise that I'm not > > looking for alternate platform/technology suggestions.- Hide quoted text - > > - Show quoted text -
