Re: VB6, VB2005, or Something Else?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I agree that MS ain't gonna fix anything for us.

I do too, but that doesn't mean I think it's right.

The problem was their decision to "break" it in the first place. The "real"
reason they broke things may be as simple as.... a new VB dev team took
over, couldn't make heads/tails out of what the previous dev team was
working on and decided to just make a split at that point (we've done that
here... but maintained binary compatibity <g>)

That would be hugely irresponsible for the number of actual users VB has,
but then again, any excuse for doing what they did is hugely irresponsible.

Since I doubt the new dev team ever touched VB until it was dropped in
their lap, they don't know what all the hoopla is about... it's just a toy
for hobbyists after all ;-)

<Grrrrrrrrrr>

A bit OT but... have to seen sample code in MSDN? For the most part, it's
terrible. I can only imagine what the "guts" look like in Windows or
Visual Studio if the same people that write the samples are the ones
writing the code for the OS/Dev tools.

Yeah, I know. :(

They >really< need to consider visiting the newsgroups for advice more
often ;-)

That's for sure!

--
Bob Comer



"Ken Halter" <Ken_Halter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%237sXQgyXGHA.4988@xxxxxxxxxxxxxxxxxxxxxxx
"Robert Comer" <bobcomer@xxxxxxxxxxxxxx> wrote in message
news:%23K$liYyXGHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
Unfortunately I'm not hearing the same thing from others.

Here it's a money issue, there is no budget for such a huge undertaking.
I don't work for a software shop, I work for a manufacturer, code is a
costcenter only, not an asset, any change has to have some serious ROI to
get through. And I'm sorry, but .NET has *none* in this setting.

Same deal here. With doc re-writes, retests, 3rd party retests, certs,
etc, costs go through the roof.

The problems are not going to fix
themselves and Microsoft is *not* going to fix it for you.

They should, and for two reasons -- one, to sell us something and make
money, and another, to regain trust they lost.

--
Bob Comer

I agree that MS ain't gonna fix anything for us. The problem was their
decision to "break" it in the first place. The "real" reason they broke
things may be as simple as.... a new VB dev team took over, couldn't make
heads/tails out of what the previous dev team was working on and decided
to just make a split at that point (we've done that here... but maintained
binary compatibity <g>) Since I doubt the new dev team ever touched VB
until it was dropped in their lap, they don't know what all the hoopla is
about... it's just a toy for hobbyists after all ;-)

A bit OT but... have to seen sample code in MSDN? For the most part, it's
terrible. I can only imagine what the "guts" look like in Windows or
Visual Studio if the same people that write the samples are the ones
writing the code for the OS/Dev tools. They >really< need to consider
visiting the newsgroups for advice more often ;-)

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm



.