Hi Doug et al:
The script that does not seem to be working is a VB.net script created in the
VB.net IDE which is almost identical to the Visual Studio IDE but for only
VB.net language applications.
I have not tried any other external languages like java or Python which do not
run under the Microsoft Framework nor C# which would be the only other language
I know under the Microsoft Framework.
I would be glad to try a non Microsoft Language, outside the Microsoft
Framework environment, but I don't know any of them well enough to try a com
interface.
I will go back and try another MSAA Event to see if it seems to work and post
up the code and results.
If any of you guys are familiar with Visual Studio or VB.net in particular my
version is Vb.net Express 2008 and I can send you the project you can load into
your IDE if you want. I think it will include all the references since I think
I put them in the bin.
Otherwise I can send you whatever you need like the Main Module code which is
actually all the relevant executable code except my Logger which is only a
print utility.
I'll get at this as soon as I can and post up the results of the new test with
a second MSAA Event test.
I will actually run one more test, in that one everything will be the same as
it now stands without modification except I will make the Global
MyMSAAEventSource variable private to see if that stops the bleeding of the
ConnectEvent from my VBScript into the VB.net Script and post the result of
that test with the above mentioned second Msaa Event test.
Later Guys and thanks:
Rick USA
