Re: Moving On

"Robert Comer" <bobcomer-removeme-@xxxxxxxxxxxxxx> wrote in message
news:%23$78xiN4GHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
1. I have enjoyed immensely being part of this group.
2. VB has served me well and has provided a good living for me for
many years.
3. I am thankfull for the excellent support provided by the people in
this group

Same here. I'm usually just a lurker here as VB programming isn't my main
job, but I get a lot out of this group!

However...

1. I don't believe VB6/5 folks have been deserted by Microsoft

In some ways yes, but no upgrade path is a KILLER for those of us with
large codebases. I don't consider a forced rewrite as support. I've been
through numerous language upgrades on other platforms and none have been
this deficient in ability to upgrade.

2. If you want to continue with VBn, no problems, its still supported
in Vista

Only the runtime is supported. :(

At first, I hated VB.Net, and searched with vengance, anything that would
make .Fred look bad. Did Microsoft abondon VB users..hell yes...or did
they?

I don't care if it looks good or bad, it's just a language like VB is just
a language, I really don't have an overall preference when it comes to
such things, they all have their good points and bad points, but I do care
how much it's going to cost to implement something and will it continue to
work for a long time.

Stay with VBn...or move to Power Basic, Delphi...et al. Not much
commercial value in any of these, other than legacy support..

I'm staying with VB6 here for the existing codebase.

--
Bob Comer



"Harry Strybos" <harry@xxxxxxxxxxxxx> wrote in message
news:l2LRg.35625$rP1.35401@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All

While I will be the target of some reactionary flamming, I would like to
make the following comments:

1. I have enjoyed immensely being part of this group.
2. VB has served me well and has provided a good living for me for
many years.
3. I am thankfull for the excellent support provided by the people in
this group

However...

1. I don't believe VB6/5 folks have been deserted by Microsoft
2. If you want to continue with VBn, no problems, its still supported
in Vista

At first, I hated VB.Net, and searched with vengance, anything that would
make .Fred look bad. Did Microsoft abondon VB users..hell yes...or did
they?

I hung onto every adverse comment made within this group as something
that would substantiate the crime Microsoft had committed. Jerry French
caused my fragile ego to feel condemmed even for abandoning V5. The much
hallowed Randy Birch (and he has made huge contributions to programmers
worldwide) even caused me to feel righteous at my indignation with
Microsoft.

Moving on...

Stay with VBn...or move to Power Basic, Delphi...et al. Not much
commercial value in any of these, other than legacy support..

VB.Net takes some work, a shift in your programming paradign to fully OO
concepts. VB.Net 2005 has some brilliant stuff. Just to get a connection
to a database is so easy... Binding is just native, classes are
everything you want. Microsoft has made an enormous effort to help VBer's
move on. Every single shortfall of VB classic has been addressed and
more.

Sorry for causing offence to some of you. The brilliance of programmers I
have mentioned above would be hugely enhanced by VB.Net. Randy, Jerry and
others, what about using your excellent skills to enhance the next
generation rather that lock people into a language that has become
static. I am not saying that you abandon VBn, just stop telling users of
this group that the world ends with VB classic. VB, as we used to know
it, is dead...that will not change. Your skills are enhanced with VB.Net,
provided you can let go of your predjudices. Lets all move on.

Cheers

Harry Strybos



Thanks guys for not being too unkind to me. Before I start, I am nobody
other that a developer. I started my work life as an Armament Technician in
the Australian Air Force and have been taught software development by an
amateur...me.

You're comments were all well received and were all worthy. I will continue
to show the utmost respect for the people in this group that have provided
valuable assistance to literally millions of VB programmers.

VB7 would have been an easy task for Microsoft. The information I have at
hand tells me that MS actually did all the design work. At the end of the
day, it was probably too huge a shift in paradigm to make the language
easily upgradeable to the next generation of computer languages. Just to
upgrade code from the much used "ComboBox" control is nearly impossible.

The VB.Net ComboBox deals with objects, rather than Name/Value pairs. Took
me a while to get a hold of that, but the new way is so powerful. I can
populate a combo box with a collection of business objects and set a local
variable of the same type to equal the selected item in the combo box.

I am an IT Manager (and Senior Developer) of an international cash flow
management company, and we have had to look at the future. Had it not been
for VBn, none of this would have happened for me. Having said that, VBn does
not cut it for the "convergence paradigm" we wish to subscribe to.

The comments made about VB.Net not being suitable for desktop applications
is in some way, correct, and does require some reasonably expensive
obfuscation software to protect you code investment. Having said that,
VB.Net does provide "one touch" delivery to your clients...much nicer than
issuing upgrades (and the associated dll hell).

I am not on the payroll of Microsoft, just a guy that leaned "heaps" from
you guys and enabled me to move on. You don't have to change to VB.Net.

Thanks heaps

Harry Strybos

p.s. I will still regularly visit this group and help where I can



.

Relevant Pages

  • RE: Security and EOL issues (was RE: WMF Exploit Patch released)
    ... Why not set up paid upgrade systems using annual contracts? ... The commitment on the contract is to continue to support as long as contracts are paid with the restriction that the needed support mst be technically feasible and as timely notification as is possible when support is not technically feasible will be provided. ... While I sympathies with those that feel that Microsoft is getting richer ... Compare AIX to Windows, ...
    (Security-Basics)
  • RE: Table ranges do not work in multilingual configurations
    ... When you create a workbook in the German version of Microsoft Office, ... the user switches the UI language. ... consulting Excel Product team, to see if there is a method to make a pivot ... Microsoft Online Community Support ...
    (microsoft.public.excel.programming)
  • Re: upgrade from 2004 to 2005 media center software
    ... >> I am afraid that you will have no luck in getting an upgrade. ... >> extremely bad at support on this issue. ... >> Microsoft and my PC manufacturer about this, ... >>> I have a HP media center 873n and would like to upgrade to the media center ...
    (microsoft.public.windows.mediacenter)
  • Re: Why should I eschew prototype.js?
    ... Microsoft drives this market, whether people admit it or not. ... out next week and proclaimed "The only markup language we will support ... Furthermore, if any other attributes are present, IE will ignore the script block. ...
    (comp.lang.javascript)
  • Re: How do I get Microsoft to fulfil their legal obligation to pro
    ... Assuming that yours is an OEM version (and it apparently is, ... it won't do an upgrade) contacting Microsoft will be of no use. ... provide any support for an OEM version. ...
    (microsoft.public.windowsxp.general)
Quantcast