Re: Preferred VB COM Development Environment?


"Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
news:RP6dnWKonM5xdxDYnZ2dnUVZ_oCmnZ2d@xxxxxxxxxxxxxxx
"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:EcKdnT_Hnf2vWRDYnZ2dnUVZ_h63nZ2d@xxxxxxxxxxxxxxx

"Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
news:ttydnQDt9emzUxHYnZ2dnUVZ_oS3nZ2d@xxxxxxxxxxxxxxx
What is the recommended platform for developing Visual Basic COM
applications under Windows 2003 or Windows XP? Visual Studio / VB 6
install fine under Windows XP, but we had terrible problems getting
them
to
work correctly under Windows 2003.

If we install VB.Net or Visual Studio 2005, is there still legacy
support
there for developing VB COM applications? Is there any reason to
prefer
developing COM applications in VB in either of those environments?


There is no "legacy" support for COM in dotNet.

You can create COM components and utilize COM components in dotNet using
'Interopt', but as the name implies it is more a emulator or translator
than
true 'COM' and contains some subtle limitations.

[I will likely get flamed for the above statement. And you will soon
hear
from others that say they are experiencing no problems. IMHO, that is
because they are willing to settle for a subset. But it is a matter of
degrees and what results you are expecting. In your problem domain -
Interopt may be entirely adequate.]

If I understand your question, Apps developed on Win2k can be run on
Win2003/XP and even Vista. (It it is the development environment and the
IDE
that causes issues). So one can just use Win2k as the development box.
We
do
all VB6/COM development on Win2k boxes with an XP on the side for
testing.
But MS is in the process of killing off Win2k.

If you need to develop ActiveX components for newer O/Ss, on those
platforms, then VC++/ATL/MFC is the best tool. Unfortunately, perhaps a
step
backwards. <g>

So, to make the recommendation explicit, stick with Visual Studio 6.0?


Sure, if it serves your purpose.

Any reasons to not install Visual Studio 6.0 on Windows XP?

No reason at all.


.

Relevant Pages

  • Install VS 2003 on XP x64
    ... I'd like to install Visual Studio .NET 2003 on Windows XP Professional x64 ...
    (microsoft.public.vsnet.setup)
  • Re: WF in .net 3
    ... You will want to be running SP-1 of Visual Studio ... To configure your computer so that you can work with WPF you should follow ... this automatically comes with Windows Vista, if you are using Windows XP ... Download and install the Windows SDK. ...
    (microsoft.public.dotnet.general)
  • Re: Binary incompatibility of Linux distributions
    ... Compared to the Windows world, yes it is a lot easier. ... To do something similar on Windows, you would have to install Visual ... Studio, which is very expensive, or Visual Studio Express, which doesn't ... because I always install my Ubuntu "the Debian way" ...
    (Ubuntu)
  • VS .NET initial web setup: No option to defer installation of updates
    ... Microsoft Visual Studio .NET Prerequisites include "Web Project ... When installing FrontPage Server Extensions, ... restarting, I could then proceed to the download and install service, ... Windows XP Media ...
    (microsoft.public.vsnet.setup)
  • Re: VS2005 and .Net Framework 3.0
    ... You need to load a .NET 3.0 Extensions for VS.NET 2005: ... SP-1 for Visual Studio 2005. ... While this automatically comes with Windows Vista, ... Download and install the Windows SDK. ...
    (microsoft.public.dotnet.languages.vb)
Loading