Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

.NET 2.0 ActiveX Control Gotchas (Safe for Scripting and Hooking into Events)

Rick Minerich's Development Wonderland — Wed, 03 Jun 2009 20:43:05 GMT

I’ve recently been building an ActiveX Control in .NET 2.0 and thought I would share some of the problems

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

ThomThom1969 — Fri, 22 Dec 2006 22:04:02 GMT

I'd also like to see a blog entry on making WSCs implement arbitrary interfaces, if you can find the time one of these days.

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

sil — Wed, 02 Jun 2004 01:03:00 GMT

Ah. If it is possible to get them to implement arbitrary interfaces then I'd be highly interested in that blog post! I really was trying to avoid writing something and then compiling it when I could just do it in script...

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

Eric Lippert — Tue, 01 Jun 2004 22:25:00 GMT

Sure, they're real COM objects. They might not implement the interfaces that a particular environment requires though.

I don't know what the requirements are for Outlook addins.

There are ways to make WSC's implement arbitrary interfaces, but its quite tricky. Maybe I'll blog about that at some point.

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

sil — Tue, 01 Jun 2004 22:09:00 GMT

I've used GetObject in the past to create a scripting component. I was under the impression that it creates a real COM object; after all, you can give WSCs a name (Foo.Bar, or whatever) and register them, but I don't seem to be able to use them in a few environments that require a COM object -- like, say, as an Outlook COM addin. Are they not *really* COM objects?

GetObject and Security

Office Development, Security, Randomness... — Mon, 26 Jan 2004 10:25:00 GMT

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

Michael Harris — Thu, 15 Jan 2004 23:59:00 GMT

And the GetObject doc error exists in the JScript.Net docs as well :-)...

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

Alex Angelopoulos — Thu, 15 Jan 2004 08:59:00 GMT

"...people will continue to use the twentieth-century COM scripting interfaces for some time yet..."

Going off on a tangent from your actual topic... :)

Any interest in blogging on WSH/.NET transition and interop issues? Some of it can be rather mundane, but there are some intriguing ways to exploit them as a team.

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

Eric Lippert — Thu, 15 Jan 2004 07:19:00 GMT

Yeah, I found that doc error some time ago. We have not had full-time staff to work on fixing up the scripting documentation for a long, long time, so there are many of these small errors "batched up" waiting for the day when someone has the time to fix them all at once. (I wouldn't hold my breath waiting for that day...)

re: Script And IE Security Part Three: Some Object Creation Techniques Are Explicitly Forbidden

Michael Harris — Thu, 15 Jan 2004 01:57:00 GMT

OK, you win, but I still have hope of *some* day catching you in an error <vbg>!

Rule #1 - test before posting...
Rule #2 - don't trust the [JScript] documentation...

With Word open, the following JScript run under WSH *does* work though the documentation of JScript's version of GetObject says essentially the same thing as the VBScript version WRT omitting the 1st argument (running instance) vs. an empty string (new instance)...

var word = GetObject("", "Word.Application");
WScript.Echo(word.ActiveDocument.Name);
word.Quit();