stanl
09-17-2011, 07:57 AM
Accessing .NET from COM is a much discussed topic. VBA and VBScript both seem to share CreateObject() functionality, so consider this code:
Set df=Dotnetfactory.CreateInstance("System.DateTime")
which is VBScipt code for accessing the DotNetFactory.dll packaged with HP's QTP. Supposedly, this dll allows access to .NET functions and properties and therefore, IMHO: acts like a bridge between COM and .NET -
If used outside QTP, might one assume it enhances COM to include .NET assemblies.
Of course, the dll cannot be downloaded separately, at least as far as I have searched.
My question is then questions: has anyone else looked into the DotNetFactory.dll; can it be licensed separately; are there limits to what it can access, i.e. dlls you create in C#; can it ever apply to VBA??????
...like I said, just for discussion:dunno
Set df=Dotnetfactory.CreateInstance("System.DateTime")
which is VBScipt code for accessing the DotNetFactory.dll packaged with HP's QTP. Supposedly, this dll allows access to .NET functions and properties and therefore, IMHO: acts like a bridge between COM and .NET -
If used outside QTP, might one assume it enhances COM to include .NET assemblies.
Of course, the dll cannot be downloaded separately, at least as far as I have searched.
My question is then questions: has anyone else looked into the DotNetFactory.dll; can it be licensed separately; are there limits to what it can access, i.e. dlls you create in C#; can it ever apply to VBA??????
...like I said, just for discussion:dunno