John said:
Hello everybody,
I just wondered if anybody else has noticed this?
It takes around 6 seconds to start debugging a very simple ASPX page
with VS.NET whereas VB6 takes under 0.5 seconds, even with
very large and complex projects.
This is a real shame
John Rivers
Of course it's slower. It's all being *compiled*, rather than
interpreted. Before it can start, all of the code behind has to be
compiled into a DLL, and then the start page (or possibly a batch of
pages, depends on some settings) have to be compiled. With the result
that once you're up and running and the pages you're using are
compiled, access to them is a lot quicker.
As opposed to ASP attitude of "we'll interpret it afresh every time" -
which only needs a text file on the file system, but is going to be
orders of magnitude slower for typical normal usage, and the VB6
attitude of "I'll start running your program fine, but there may be a
massive chunk of it that can't actually compile - we'll find out when
you get there". Hence the seperate Ctrl-F5 method of starting debugging
which takes a lot longer (and which was the worst bit, for me, of
adapting to VB.NET - Starting a program with Ctrl-F5, and watching it
zoom past all of my breakpoints)
Damien