Hi all.

Does anyone know if VB dotnet can be used to create ActiveX components that
operate different versions side-by-side?

Thanks.

Side-By-Side installation should be a matter of the setup program, not the
ActiveX development tool.  You should be able to specify SBS installation of
even old OCX controls in a setup package like Visual Studio Installer, Wise,
or InstallShield.

ScottD

Not entirely; DLLs which used shared memory
segments and other programmer tricks can
ensure that side-by-side doesn't work.

Agreed; I can't think of anything in VB 6, VB.NET
or VC.Net that would prohibit side-by-side
(unless the programmer coded something that
screws things up).

My impression from VBITS is that you can create .NET components that will
work side by side.  These components don't have GUIDS and don't need
registry entries.  For backwards compatibility, projects will have the
ability to treat ActiveX (COM) objects as .NET objects and even vice-versa.
However, this does not change the fundamental behavior of ActiveX objects,
so you won't be able to do anything with them that you couldn't do already.