"p byers" <email@example.com> wrote in message
> Sadly both of these links relate to dotNET
> At the moment, I do NOT want to move to dotNET
> Thanks for the reply though
That box on so many of the MSDN web pages is misleading. It says:
This page is specific to .NET Framework 3.0
Other versions are also available for the following:
Microsoft Visual Studio 2005/.NET Framework 2.0
It is not the information on the page that is specific to .NET.
Perhaps there is something about the HTML that is specific to .NET.
If you take the link to the 'Other versions', you get the same
information, and a similar box leading back to this .NET Framework 3.0
page. I think the box is just a disinformation scheme.
> McKirahan wrote:
>> "p byers" <firstname.lastname@example.org> wrote in message
>> > Hi Folks
>> > Is it technically possible to take one or more VBS functions
>> > and put them into an ActiveX DLL.
>> > If so, where can I find the documentation to show me how to
>> > do it ??
>> > Classic that is, NOT dotNET
>> "Windows® Script Components provide you with an easy way to
>> create powerful, reusable COM components in script. You create
>> script components using any scripting language that supports the
>> Microsoft® ActiveX® Scripting interfaces. Script languages that
>> support these interfaces include JScript, Microsoft® Visual Basic®
>> Scripting Edition (VBScript), PERLScript, PScript, and Python."
>> Introducing Windows Script Components
>> Building Windows Script Components