Is there a good article anywhere discussing the differences between
the version of VB.Net that you get with VB.Net 2003 Standard and the
version you get with Visual Studio.Net professional?
I have looked at the microsoft site, but it is not very clear. It
seems that there are some differences between the standard and
professional versions of VB.Net, and I understand that you cannot get
the professional version stand-alone (only as part of Visual Studio).
What I am unclear of is exactly what the difference between the
standard and professional versions of VB.Net are.
I have been using VB 6.0 for years, and we are starting a new project
and we thought it might be worth taking the plunge and upgrading to
VB.Net. I understand that any new code written in VB.Net can call
existing activeX components written in VB6, but it is not clear
whether I can create new ActiveX controls with the standard edition of
VB.Net. The MS website says that the standard edition does not allow
you to: "Build reusable Windows and Web controls". Does this mean that
I cannot create new OCXs activeX DLLs etc... without buying the whole
VS suite?
TIA
Phil.

"Phil Preen" <phil (AT) triton-technology (DOT) co.uk> schrieb:
The Standard edition is lacking project templates for class library/control
library projects. These templates are included in the Professional edition.
Notice that you cannot create ActiveX controls using VB.NET at all, you can
create .NET Windows Forms controls instead. I suggest to get the
Professional edition if you are planning to do professional/commercial
development.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

version. It is a pity that you cannot get this without going for the
whole studio suite, as this makes it significantly more expensive, and
contains lots of other stuff that we're unlikely ever to need.

I am a little concerned that you cannot create activeX components using
VB.Net. We will need to create components that can work within Excel
and possibly other office applications. Currently we often do this by
creating an ActiveX DLL in VB6 and this is invoked from a VBA macro
using CreateObject. We may also wish to embed objects (controls??)
directly in Excel worksheets or charts. How is this achieved with .Net?
Thanks,
Phil.