Hi

Will VS.NET 2003 have debugging while running like vb6?

Does anyone know?

Peter

E&C (Edit & Continue) is not in VS.NET 2003 - this slated for V2 of the
framework, which is the next release.  This is 1.1.

Personally, I couldn't care less E&C is no big loss in my book.

Tom Shelton

While I like editing on the fly, I find that I do less seek and destroy
debugging in .NET, due to the paradigm change. As such, I rarely miss edit
and continue (although there are instances).

In most cases, by changing the output of a function, rather than the code
(ie, change variable values), I can mimic the changes the code would enact
and see if the change is worthwhile before even running it.

One of the problems with debugging in VB 6, which is the reason why edit and
continue is so easy, is you debug P-code, not truly compiled code. As .NET
is IL, this may not be an issue.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think outside the box!
****************************************************************************
****

I agree.  When you compile in VB.Net, it shows all the errors rather than
just one at a time.  

-- If you don't like lunchmeat, please remove it from my e-mail address to
send me an e-mail

On Fri, 22 Nov 2002 11:15:23 -0600, "Cowboy \(Gregory A. Beamer\)"

That's true, but sometimes it is a BIG advantage. We do a lot of
database conversions for customers who are going to use our product
and databases. Sometimes database fields are 'reused' so the
conversion program will sometimes stop because it gets wrong data.
In VB6 we used the inline de{*filter*} to make a small work around and the
conversion continues. Now you have to stop and start from the
beginning which cost a lot of time. (sometimes conversions are running
6 hours and when you than get an error at the end...........)

Peter