Re: Upgrade via VB6???

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Wed, 22 Aug 2007 14:25:08 +0200, "Schmidt" <sss@xxxxxxxxx> wrote:

¤ > COM is not VB.
¤ But VB is COM.

VB implements COM in addition to supporting other features and extensions. Failure to support any of
these features or extensions can cause Visual Basic to fail, irrespective of COM.

¤ > Just because they support COM doesn't mean that
¤ > Classic Visual Basic applications
¤ > will continue to function as expected.
¤ If VB is COM then - yes, of course will they work.

VB is not COM.

¤ > ¤ I think, if MS decides, that the newest Office 2007 should
¤ > ¤ run on the Vista-successor, then all other COM-based
¤ > ¤ Apps should run too.
¤ >
¤ > This is very overly simplistic thinking.
¤ > COM is an architecture. It doesn't determine whether a
¤ > feature of the operating system is rendered inoperable,
¤ > incompatible or obsolete with respect to an
¤ > implementation.
¤ If COM cannot work with the Vista-Successor, because
¤ COM is an "architecture", then also MS Office 2007 will not
¤ work anymore - and also the whole bunch of all other
¤ COM-Apps out there.

VB is not COM, nor is it Office 2007.

¤ > ¤ > ...or are not supported at all.
¤ > ¤ As said, I'd be interested in a small Demo-App, wich does
¤ > ¤ something useful and is based on these "not supported
¤ > ¤ features", available only for .NET.
¤ >
¤ > Sure, create a web service in Classic Visual Basic.
¤ Then you probably should create a small Demo-App around
¤ a WebService (wich does something useful, e.g. transferring
¤ Recordset-Data to a client and visualize) - and I come
¤ back with the VB-Pendant, wich does the same - then
¤ we can compare e.g. lines of code and performance.

Here you go:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q301273&ID=KB;EN-US;Q301273

¤ > ¤ > Our apps aren't limited to the desktop. We need
¤ > ¤ > enterprise solutions, which involves the development
¤ > ¤ > of both desktop and web based apps...
¤
¤ > ¤ Just because of interest - can I see one of your web-based
¤ > ¤ Applications in action, for wich you also developed an
¤ > ¤ appropriate desktop-pendant?
¤ >
¤ > I don't understand your question.
¤ I simply doubt your statement - if it is right, then you should
¤ be able to show me at least the Web-Part of such an
¤ "Dual-Application" - that's all.
¤ > We use an integrated environment for both types of apps.
¤ Yep, that's what you already said, but "where's the beef"?

I don't think you understand. Classic Visual Basic does not provide the features I've already
documented. You have to operate outside of the environment, or in a different environment, in order
to do some of what I have suggested.

¤ > The only difference seems to be that you don't have
¤ > the same requirements as I.
¤ Maybe, but what I don't understand is:
¤ You have a requirement.
¤ You are saying, that you use a tool that is highly
¤ productive to fulfill that requirement.
¤ And I'm just asking: "Where is your output then? -
¤ it should be huge!"

Where is our output? If you mean applications, then they're running on our servers or in our desktop
environment.


Paul
~~~~
Microsoft MVP (Visual Basic)
.

Relevant Pages

  • Re: VB AND VB.NET
    ... I want to be able to do so when the features change and I have ... a valid reason for the rewrite, language not withstanding, not just ... features and language constructs of VB.NET. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 and Beyond
    ... ¤ non-functional as MS abandons support for the language? ... Third-party support, one of the greatest features of Classic ... Microsoft MVP ...
    (microsoft.public.vb.general.discussion)
  • Re: Upgrade via VB6???
    ... ¤> ¤ But VB is COM. ... If the Vista-Successor doesn't support the Windows-API, ... I can develop desktop apps and components but that's about as far as it goes. ... of an "integrated environment for both types of apps". ...
    (microsoft.public.vb.general.discussion)
  • Re: Back to VB6 and .NET
    ... ¤> Windows 2000 and Windows ME mainstream support has ended. ... still expect to use new features on obsolete systems. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB 6 vs VB.NET
    ... ¤ outdated in near future. ... capabilities as no new features will be added or existing bugs or incompatibilities fixed. ... You must learn new features in the .NET Framework in order to work with Visual ... primarily because I still have to support applications or COM components developed ...
    (microsoft.public.vb.general.discussion)