Yesterday my last programmer left my project so now I'm just down to me. No
one wants to work on vb6 anymore! I'm only on the project 2 days a week
myself because I don't want to do vb6 either. It's getting to the stage that
it needs to be upgraded to dotnet just to keep the programmers.

"Michael C" <nospam> wrote in message
news:3364
> Yesterday my last programmer left my project so now I'm just down to me.
> No one wants to work on vb6 anymore! I'm only on the project 2 days a week
> myself because I don't want to do vb6 either. It's getting to the stage
> that it needs to be upgraded to dotnet just to keep the programmers.

From memory, aren't you from .au? Melbourne?
If so, If you are interested in a weekend developer, let me know - mdc222 at
yahoo com au

> Yesterday my last programmer left my project so now I'm just down to me.
No
> one wants to work on vb6 anymore! I'm only on the project 2 days a week
> myself because I don't want to do vb6 either. It's getting to the stage
that
> it needs to be upgraded to dotnet just to keep the programmers.
>
That is discouraging. Maybe this will cheer you up:

http://www.panopticoncentral.net/arc.../03/13539.aspx

It's an MS blog explaining that although the author
thinks VB.Net 2005 is very much ship-shape, the
gang has nevertheless issued a patch to fix "a number
of problems that we've isolated". It's worth the read
just for the entertainment value of that sort of MS
double speak. (...."Although the patient was never
fatally ill before, he woke up dead"...."Although
VB.Net 2005 doesn't have any problems, we've fixed
many of the ones that we found." ...)

But what might cheer you up even more is the
comments posted below the blog entry. It seems that
most 2005 users think it's a step back from 2003 and
many think it's notably inferior to VB6.

One poster says, by way of encouragement to the
".Net Team": "...but I would say VB2005 may be close
to the VB 5.0 experience."

Another poster accuses the people in charge of ignoring
the needs of .Net developers in order to "entice the VB6
crowd". :)

The last post, by one Doug Creel, is gushingly supportive
and positive...in a way. A closer reading reveals that what he's
really saying is that it's understandable 2005 was rushed to
market and that he intends to be patient in waiting for SP1!

-------------

What strikes me most about all of this is that after 5
years of .Net (an age in computer time) it's still only partially
accepted, many of the users are still depending on VB6 to
get their job done, most seem to prefer older .Net versions
to the latest, and most seem to be nothing short of appalled
by the slowness of the whole thing....And these are .Net people,
not VB6 "resistors".

... So read the link and cheer up. By the time you finish
it you'll be saying, "So long, sucker" to your exiting
programmers.

(PS - By the way, if you want the patch that allegedly might
fix some of the 2005 problems, you have to call Microsoft
on the phone!)

"mayayana" <mayaXXyana1a> wrote in message
news:4419
> [..]
>
> It's an MS blog explaining that although the author
> thinks VB.Net 2005 is very much ship-shape, the
> gang has nevertheless issued a patch to fix "a number
> of problems that we've isolated". It's worth the read
> just for the entertainment value of that sort of MS
> double speak. (...."Although the patient was never
> fatally ill before, he woke up dead"...."Although
> VB.Net 2005 doesn't have any problems, we've fixed
> many of the ones that we found." ...)

That's not really true. What they said was it was a solid release but
they've fixed some performance issues with large projects and visual basic.
They never said the product was bug free but we've fixed the bugs. C# is
more aimed for large projects so I guess these companies should be using it.

> But what might cheer you up even more is the
> comments posted below the blog entry. It seems that
> most 2005 users think it's a step back from 2003 and
> many think it's notably inferior to VB6.

I haven't used 2005 yet but I didn't get that impression from the responses.
I presume they change on a regular basis so I'd have to go searching.

> One poster says, by way of encouragement to the
> ".Net Team": "...but I would say VB2005 may be close
> to the VB 5.0 experience."

People say the stupidest things on the internet*. I'm sure it's got faults
but to compare it to vb5 is just plain stupid.

Michael

*Actually it's not restricted to the internet. :-)

"Michael Cole" <noone> wrote in message
news:1216
> From memory, aren't you from .au? Melbourne?

I am.

> If so, If you are interested in a weekend developer, let me know - mdc222
> at yahoo com au

They might be interested in a full time developer but I wouldn't recommend
working here. :-)

Michael

"Michael C" <nospam> wrote in message
news:3364
> Yesterday my last programmer left my project so now I'm just down to me.
> No one wants to work on vb6 anymore! I'm only on the project 2 days a week
> myself because I don't want to do vb6 either. It's getting to the stage
> that it needs to be upgraded to dotnet just to keep the programmers.

Have you ever heard of crossposting?

<snipped>

> by the slowness of the whole thing....And these are .Net people,
> not VB6 "resistors".

So does that mean that VB6 skills can be measured with an ohmmeter?

Saga

"mayayana" <mayaXXyana1a> wrote in message
news:oRwEg.6532$Qf.4419
> One poster says, by way of encouragement to the
> ".Net Team": "...but I would say VB2005 may be close
> to the VB 5.0 experience."

ROTFLMAO

They really need to wake up to the fact that VB.Net serves no useful purpose
and just kill it off. They can then concentrate on C# and maybe even start
to consider some sort of VB-to-dotnet migration path.

On Wed, 16 Aug 2006 04:06:44 GMT, "mayayana" <mayaXXyana1a>
wrote:

>> Yesterday my last programmer left my project so now I'm just down to me.

<snipped/>

> That is discouraging. Maybe this will cheer you up:
>
>[..]
>
> It's an MS blog explaining that although the author
>thinks VB.Net 2005 is very much ship-shape, the
>gang has nevertheless issued a patch to fix "a number
>of problems that we've isolated". It's worth the read
>just for the entertainment value of that sort of MS
>double speak. (...."Although the patient was never
>fatally ill before, he woke up dead"...."Although
>VB.Net 2005 doesn't have any problems, we've fixed
>many of the ones that we found." ...)

Quite an interesting read, Mayayana. Thank you!
_______________________
Michael B. Johnson

<snip>
>> One poster says, by way of encouragement to the
>> ".Net Team": "...but I would say VB2005 may be close
>> to the VB 5.0 experience."
>
> People say the stupidest things on the internet*. I'm sure it's got faults
> but to compare it to vb5 is just plain stupid.
>

This is very true since with VB5 one was programming a computer (with a
little persistence and a lot of API), but with .Net one is programming
Windows (API?? What's API?), and tightening Bill's grip on the collective
nuts of the development world.

OOh! A gratuitous snipe at Micro$oft .. whatever next!


MFK

"Ken Halter" <Ken_Halter> wrote in message
news:1272
> "Michael C" <nospam> wrote in message
> news:3364
>> Yesterday my last programmer left my project so now I'm just down to me.
>> No one wants to work on vb6 anymore! I'm only on the project 2 days a
>> week myself because I don't want to do vb6 either. It's getting to the
>> stage that it needs to be upgraded to dotnet just to keep the
>> programmers.
>
> Have you ever heard of crossposting?

As I said in the other thread this was a genuine mistake. I thought ms
considered damn a swearword and killed the post so I posted again. I'd just
posted in a different group to what I expected. I have never multiposted and
only *very* rarely cross posted.

Michael

"Michael Keating" <michael.keating> wrote in message
news:nz2d
> This is very true since with VB5 one was programming a computer (with a
> little persistence and a lot of API), but with .Net one is programming
> Windows (API?? What's API?), and tightening Bill's grip on the collective
> nuts of the development world.

Hang on a sec. Aren't we programming less of a windows based language? In
VB6 the form/control/usercontrol was built in and could not be
removed/replaced. In dot net the forms dll is just another *optional*
reference and can be removed/replaced.

Michael