kimiraikkonen

On Oct 19, 2:20 am, John B <jbngs...@yahoo.com> wrote:
> Peter Duniho wrote:
> > John B wrote:
> >> This is not a bug.
>
> > I think that's probably true. But...
>
> >> c# doesnt do continual incremental builds as vb.net does (this is a
> >> good thing) and therefore does not have the ability to highlight
> >> syntax errors "on-the-fly".
>
> > That's definitely not true. In the retail Visual Studio 2005 that I
> > use, C# is constantly evaluating what I type, highlighting errors and
> > listing them in the error output pane.
>
> Hmm, seems you're correct.
> It never used to(I think) in 2003, personally I have the error window
> minimized to maximise code realestate.
> It seems finicky about what it picks up though.
> If I miscase a variable name or misspell a type name, it doesn't pick it
> up until compile time (VB.NET does).
>
> VB.NET highlights the actual lines in the code window too.
>
> Thanks,
>
> JB

At least, Visual C# is very late for reflecting on-the-fly error
reporting. VB.NET reports errors immediately after you finish typing
syntax or jump to another lines. But i saw in C# express (2005),
there's a delay, latency about reporting errors, you must click
somewhere or try to debug it to see if there are really errors.

However, it might be about C# coding discipline, structure or sth
else.

Thanks.

Jon Skeet [C# MVP]

On Oct 19, 11:54 am, kimiraikkonen <kimiraikkone...@gmail.com> wrote:

<snip>

> At least, Visual C# is very late for reflecting on-the-fly error
> reporting. VB.NET reports errors immediately after you finish typing
> syntax or jump to another lines. But i saw in C# express (2005),
> there's a delay, latency about reporting errors, you must click
> somewhere or try to debug it to see if there are really errors.

Again, this is not something I've seen, though it's been a while since
I've used Express.
As I use ReSharper, it's hard to say what the "vanilla" 2005 C#
experience is, but if I type a statement without a semi-colon, for
instance, it's highlighted less than a second later. That's perfectly
acceptable as far as I'm concerned.

You *certainly* don't have to debug it though - compiling it will be
enough.

Jon