Re: How's dot.net doing nowadays?


"Robert Conley" <robertsconley@xxxxxxxxx> schrieb im Newsbeitrag
news:a673c90d-d02c-4bc0-a55e-fa67de2cb526@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Just curious...
Do you have some examples about those
problems, which would be gone in .NET?

One biggie is the stack trace available when you get an error.
Do you mean something like the <Ctrl><L>,
which is available for Debugging in VB-Classic?

Another that is available in 2005 and above to the
ability to define a strongly typed collection code in
about three lines of code thanks to
inheritance and generics.
Agreed, that is nice, but not a "blocking issue".

Multi-tasking and other tradition C++ APIs are now
exposed. And there are other which basically can be
summed up as you code more functionality in less lines
of code with a richer API.
Yes, the "base library" is more rich, but in VB-Classic
there are usually (at least after some years of coding a
larger project in VB-Classic) other libraries or tools
bought or written over time, which should match the
functionality of those .NET-baseclasses very well -
resulting in Lines of Code, very similar to what
you would have to write in .NET.

My question to Chris Anderson was caused by
his statement, that there are problems in a VB-
Classic-App (developed over years), which
could be solved with .NET easily.
My point is, in a well written VB-Classic-App
(over years) there should be no problems, if
there are problems, then those should be able
to solve with VB-Classic itself.
And yes, in most cases an older App is based
on constructs (the selfwritten "framework" if you want),
that is not suitable (over time - when the App grows).
Then, if you get a chance to do a clean rewrite
of the App, you know better and don't make that
many "mistakes" - I think that is the effect Chris sees now,
but this is something you would see too, if you'd have used
VB-Classic for the rewrite - it is nothing related to the
"power of .NET".

Too sad, that he did not respond, what those
problems are.

Olaf
..



.