Hi Kate And Bruce: If I called it PowerBasic I was having a brain f... The scripting language that has access to the .net resources is called PowerShell. I am not sure if PowerBasic has the necessary hooks to handle something as complex as a com interface - it might. Kate, if PowerShell was somehow associated with the WE Scripting Engine like VBS then it would solve the problem of interacting with the .net framework if I read it correctly. Anyway, I am mucking about with vb.net again as a scripting language after Aaron's sample C# code. I would use C# but I hate curly Braces and a few other features of that language; So, I am trying to convert Aaron's code into Vb.net. VB.net handles Events a little diferently (syntactically) from C#. I will have to either use static or dynamic handlers and I'm not sure which will work best. Aaron uses what appears to be a Dynamic Handler approach. I think that implies late binding and may be required for the callbacks to work correctly - especially if running under a secondary process. But, I'm not sure and have found examples, my old code for one, where early binding using the With Events clause and the Handles Keyword work with com interfaces under Windows XP so I'll test both methods and post up the results. You might muck with PowerShell since you will likely end up using it if you are going to do allot of work with system Management Tools or servers to automate management processes. Ask your instructor if that is the language of choice for System or Server Administrators. If so this might be a good time to muck with it some before taking a class in it. If not, skip it and you can easily use VBS or, if I get lucky, VB.net or C#.net to create WindowEyes Apps. Rick USA
Rick USA ----- Original Message ----- From: Katherine Moss To: [email protected] Sent: Thursday, April 12, 2012 10:07 PM Subject: RE: WE And Microsoft Development Environments Oh. Jees. Okay then. Looks like I'm not even going there LOL. But I'm rather confused as to what that has to do with the issue at hand with WE scripting via .NET? From: BT [mailto:[email protected]] Sent: Thursday, April 12, 2012 8:49 PM To: [email protected] Subject: Re: WE And Microsoft Development Environments Hi Kate, I think before you go further on that, look at this and before even attempting Power Basic. Bruce http://www.vbforums.com/showthread.php?t=632684 Sent: Thursday, April 12, 2012 7:25 PM Subject: RE: WE And Microsoft Development Environments Thanks guys. And Power Basic? I don't even know what that is LOL. From: BT [mailto:[email protected]] Sent: Thursday, April 12, 2012 7:02 PM To: [email protected] Subject: Re: WE And Microsoft Development Environments Hi Kate, I attempted to send this yesterday and for some reason an error email came back saying message to large and Rick has also replied since then. Here is what I wrote and never got posted: Kate, Not that WE has trouble, Microsoft is a moving target , hard to hit, and catch up is the name of the game. All languages have issues, especially the new versions. Microsoft just likes changing the rules purposely each time they come up with new stuff. But in cases like ME, SQL Server 2008, and Vista and such Windows just writes bad stuff! So, just keep on doing what you are doing and remember the pitfalls... Bruce Sent: Wednesday, April 11, 2012 8:57 PM Subject: RE: WE And Microsoft Development Environments So that I understand, are you saying that WE has issues supporting .NET controls?
