Thanks Chip: I am off to check out those scripts. It is just what you might call a "blue sky" idea at this point. That is to be able to use the .net features from a vb script. This is only going to be good for folks developing scripts to be run on a Windows Operating system but my Visual Studio stuff would fit that bill. I tried writing a vb.net external script but never got it to work correctly. The examples and the FruitBasket samples were not set up as WindowEyes scripts against a real-world application like NotePad or Visual Studio. And, I just couldn't make the leap from a stand-alone script that could communicate with Windoweyes and coding that script to work using MSAA and all those application specific hooks. Besides, a scriptor could check if the computer is running Windows or another OS and, if Windows, might be able to then use some cool tools instead of the crude tools available in VBS - not a critisim but they seem crude compared to my experience with the .net Framework features and the Visual Studio Editors in the IDE. I think VBSEdit will help and, if we can access the .net Framework objects and methods, that would be a help to do some nice things. The .net User Interface controls are more advanced if I can access and use them and things like the StringBuilder,various Collection Types and advanced Data Handling come to mind at this moment. That said, I am not sure it will work and I am not even sure I can try it out since I only have the Express modules and building the DLL, or the Com Interface if that is the same thing as Jamal called it, might not be possible with the Express modules. One idea was to build a "Custom Control" to have available to VBS but that is out of bounds for the Express modules. My other idea is to just build a DLL if possible and then have a method to create an object like a Windows Form with other methods to set properties and execute various commands or event handling.Right now I'm not sure how that would work but it might work.Well, off to peek at those scripts you mentioned today. I am also reading up, with great confusion, on using oAuth and REST to access a DLL provided by my bank to certain Programmers - sigh. That is a real bugger since they have no useful docs that I could find so far. I am reading up on similar implementations for other Applications but the process depends to a great extent on the Application Service Provider and the Docs on using VB.net or even VWD with REST are pretty confusing and point into WCF, Windows Communications Foundation which is also quite confusing for this old brain. Well, off to do some downloading and reading of scripts this morning - at least I think I can do that without reading a hundred articles and getting more white hair - grin. Later: Rick USA
Later and thanks: Rick USA ----- Original Message ----- From: Chip Orange To: gw-scripting@gwmicro.com Sent: Thursday, March 10, 2011 9:29 PM Subject: RE: Calling DLL From VBS Rick, Jamal also has 3 apps which may be of interest to you, especially the one named "invoke .net"; there's also iron.com demo (for access .net again I believe), and homerJax (just because I wanted to list them all). I don't know enough about .net to know if these will help, but the invoke .net looks like what you're asking about. hth, Chip ------------------------------------------------------------------------------ From: RicksPlace [mailto:ofbgm...@mi.rr.com] Sent: Thursday, March 10, 2011 7:32 AM To: gw-scripting@gwmicro.com Subject: Calling DLL From VBS Hi: Has anyone called a DLL from a VBS script that runs under Windoweyes? I ask because I am wondering about creating .net scripts, registering them and then passing data to their functions, subs and properties to use the .net classes of the .net framework. For example: if I create a dll to work with a TreeView Control, I might be able to pass parameters to the methods, properties etc... of the .net TreeView and return non-typed data from it if I can define such data in VB.net or C#.net. One dll per advanced, managed UI control or other objects might give me the ability to use the .net objects. The caviot is that passing data back and forth might be a problem if there is no varient equivlant in VB.net or C#.net. That might throw a damper on this idea. Has anyone used a dll from within a Windoweyes vbs script? And, or, has anyone passed non-variant data between a vbs script app and a dll or other program? The question here would be if their is some way to convert variant and non-variant data back and forth somehow. That is where I start to get confused since I'm not sure if that can be done between VB.net and VBS. Well, this is just another thought while I take Chip's classes and read up on VBS and all that jazz. Rick USA
