Re: Msoft discontinuing VB.NET

In future, may I suggets that you try and address the problem at hand not
the individual..

I did address the problem at hand. The individual in this case, or rather,
the mindset of the individual, is the problem at hand. But because of the
mindset of the individual, the problem is not recognized. Therefore, there
is no point in continuing with this discussion.

--

Kevin Spencer
Microsoft MVP
Digital Carpenter

A man, a plan, a canal,
a palindrome that has gone to s**t.

"cmoore" <cmoore@xxxxxxxxxxxxxx> wrote in message
news:eZDniJ32GHA.3944@xxxxxxxxxxxxxxxxxxxxxxx

"Kevin Spencer" <uce@xxxxxxx> wrote in message
news:ulfJhdx2GHA.4796@xxxxxxxxxxxxxxxxxxxxxxx
The ONLY conclusion we have from the above is that MSoft want to move
customers off VB.NET, by lack of any ongoing support for VB.NET!

Your logic is flawed. In fact, there are many possible reasons for what
you
perceive to be true.
Does not change the fact that basic problems known about before vs 2005
release still have not been fixed..
Doe not matter what is the reason..
A compiler that does not work is useless..

Regarding your first point, both C# and VB.Net have
features that the other does not.
So what... the point was regarding VB.NET support for vs funtions..

Regarding your second point - I couldn't
follow your train of thought. You didn't explain what you are
experiencing
and why you have the opinion you have about what you are experiencing. As
NO, I explained about the known facts that breaking problems identified
before vs 2005 release still ahve not been fixed..

for your third point - There is a Service Pack in the works for Visual
Studio.Net (I am just guessing as to the development software you're
using,

Mmm, vs 2003 SP1 took three years, and did almost nothing, but did cause
yet
more developer probelms..
VS 2005 SP1 is on the never never plan, still stated for relase next week
(Joke), and the reality is that they are plannign a play cust sometime
this
month...

since you didn't mention any). AFAIK, the Service Pack addresses all
issues,
including any VB.Net issues.
Simple Bull..

Software has bugs in it.
DOnt care about bugs, just expect a compiler to be able to compile
anythign
otehr than trival demo appas, which VB.NET cannot do today.. See 2004/2005
outstanding reportson this... Yes outstanding still today..

Service Packs have
been around for decades. Therefore, there is nothing specific about
VB.Net
Actually not true... do some home work on VB.NET..

that can be concluded from the fact that there are bugs in the software,
of
which you seem to think the bugs in VB.Net are more severe or important.
And
you have not provided evidence that your development software (whatever
it
is, since you claimed that "VB.Net still can't compile any decent size
project without crashing" and VB.Net is a language, not a compiler)
Actually it is synomious with the compiler and not the language..

actually
has this problem, or whether this is simply something you are
experiencing
for whatever reasons, including the possibility that something is wrong
with
your system, or your methodology.

This si the typcial MSoft, it must be the custoemrs fault not ours, do you
perhaps have a vested interest with MSoft?
Anyway simply lookup there know outstanding bugs on VB.NET, these are not
one offs or limited to individuals..


Therefore, there is no logical reason to come to any conclusion that you
have proposed, especially to come to the conclusion that the "ONLY"
conclusion "we have" from your observations and perceptions is that
Microsoft is killing VB.Net.

Wrong, as your argumenst are bsed upon hype, not facts..


However, poor logic will certainly kill any software that is developed
using
poor logic. GIGO.

No head in the sand will kill MSoft...

In future, may I suggets that you try and address the problem at hand not
the individual..


--
HTH,

Kevin Spencer
Microsoft MVP
Chicken Salad Surgery

What You Seek Is What You Get.

"cmoore" <cmoore@xxxxxxxxxxxxxx> wrote in message
news:OFrm9ir2GHA.1256@xxxxxxxxxxxxxxxxxxxxxxx
Is VS 2005 the death of VB.NET?

1. Features from vs 2003 C# still have not made it into VB.NET
2. Poor support for any new features; see the hopeless refractoring
support
in VB ( one method) as an example..
3. No support for VB.NET breaking problems after almost 12 months..
- vs 2005 VB.NET still cannot compile any decent size project without
crashing..
- vs 2005 VB.NET still has basic compiler checking problems.

The ONLY conclusion we have from the above is that MSoft want to move
customers off VB.NET, by lack of any ongoing support for VB.NET!













.

Relevant Pages

  • Re: how do you start learning assembly language
    ... compiler technology for decades, and which every compiler author have ... And I have refuted your claim that monofiles are bad idea or "design lack" ... Yes, I said that if an assembler did not support linking, it ...
    (alt.lang.asm)
  • Re: Msoft discontinuing VB.NET
    ... by lack of any ongoing support for VB.NET! ... there are many possible reasons for what ... A compiler that does not work is useless.. ... the point was regarding VB.NET support for vs funtions.. ...
    (microsoft.public.vstudio.general)
  • ANN: Chicken 2.0
    ... - The compiler is able to inline more procedure calls ... - The alternative continuation API described in Marc Feeley's paper ... Hash-tables support now user-defined hash functions ...
    (comp.lang.scheme)
  • Re: Lint
    ... There are many versions of lint out there from "free" to expensive. ... Free, as in open source, will often take time to get full use of - and it may have hidden "costs" (such as license or support issues). ... Secondly, C compilers do much better static error checking than they used to as a side effect of better optimisation - while figuring out things like aliasing, variable lifetimes, and ideal memory organisation, a compiler can often spot buffer overflows and other such errors. ...
    (comp.arch.embedded)
  • CMUCL 19f released
    ... The CMUCL project is pleased to announce the release of CMUCL 19f. ... SSE2 support added for x86. ... Compiler can now derive the rank of an array, ...
    (comp.lang.lisp)
Quantcast