Re: Visual Basic 2005
From: Paul Clement (UseAdddressAtEndofMessage_at_swspectrum.com)
Date: 07/07/04
- Next message: donotspam: "Split function or Join function: delimiter problem"
- Previous message: Stephanie Stowe: "application requirements - a service?"
- In reply to: Tony Proctor: "Re: Visual Basic 2005"
- Next in thread: Schmidt: "Re: Visual Basic 2005"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 07 Jul 2004 11:56:17 -0500
On Wed, 7 Jul 2004 16:06:39 +0100, "Tony Proctor" <tony_proctor@aimtechnology_NOSPAM_.com> wrote:
¤ Sorry Paul but I have pick you up there when you say "...have chosen to...".
¤ Choice doesn't always come into it. I can be pragmatic and use any language,
¤ if the money's right. However, if your company has a significant investment
¤ in VB6 code, and the design is strongly linked to those 'environment
¤ differences' you mentioned, then you may not have a choice. Moving forward
¤ takes a redesign and a lot of resources, but cash flow may be insufficient
¤ in a small company. Where's the choice there? Jobs may be at stake as a
¤ result of the situation MS has placed such companies in. I think most of the
¤ disparaging was (or should have been) aimed at MS rather than any given
¤ language.
¤
Tony,
I'm certainly not suggesting that you completely drop your Classic VB development investment. I
haven't as I still need to support or ultimately migrate existing applications. However, in order to
insure that my applications will continue to operate in future environments and that I have the
ability to offer enhancements with respect to new features, the applications must be moved forward.
I'm not going to dispute that it may not be easy, but just the same it's necessary to survive.
I work for a small company as well. Prior to .NET our investments were in Access, Visual Basic and
ASP. Most of them still are. The transition to VB.NET and ASP.NET, while challenging at times, has
enabled us to be more efficient in our development. While there is a learning curve, it's proving to
be a benefit in the long run because we're more productive in the .NET environment.
Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)
- Next message: donotspam: "Split function or Join function: delimiter problem"
- Previous message: Stephanie Stowe: "application requirements - a service?"
- In reply to: Tony Proctor: "Re: Visual Basic 2005"
- Next in thread: Schmidt: "Re: Visual Basic 2005"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
