com

I'm trying to deal with a piece of specialized hardware, that presents it's interface as a COM object, using win32com in Python. However, the documentation for how to actually set up the hardware through the COM object is sparse (it requires a significant amount of initialization), and entirely oriented at using a bunch of pre-built libraries for Visual Studio, which are not accessible through python. That said, is there any way to watch all local COM activity, so I can sort through the activity logs to try and figure out how the existing demo programs properly initialize the hardware, and

Update : This is a confirmed bug in Silverlight 4 beta. http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=523052 I solved this issue by switching to a full blown WPF application and using regular old Microsoft.Office.Interop.Word. But I'm still very interested in how to get this to work using the dynamic values from ComAutomationFactory. This may be more of a C# 4.0 question, but what I'm trying to do is leverage the ComAutomationFactory class in a trusted SL4 app to load up a Word doc, change some text, and print it. Using a regular windows app, it's pretty easy:

I'm wondering if it is possible to call .NET functions from R, via a COM call. The library rcom allows calls to COM objects, so this should be possible, in theory, for any .NET assembly that is exposed as a COM object. To keep it simple, I'll see if I can call the .Reverse() function in System.Text , which is exposed by default as a COM object from the .NET framework. This is what I have tried so far: I obtained a list of ProgID's in my system (see link to C# code ). Here is a list of the relevant ProgIDs in my system: ---start list of COM ProgID entries--- <snip> System.SystemException ->

This is a very simple setup, I can't believe but I didn't find anybody with the same problem so far... Create a .Net4 class library in VS2010. Create a simplest possible COM object: [ComVisible(true)] [Guid("CD157EBC-C89D-40b6-B531-E85FF4B3AE9A")] [InterfaceType(ComInterfaceType.InterfaceIsIUnknown)] public interface IAcorn { bool Foo(string moo); } [ComVisible(true)] [ClassInterface(ClassInterfaceType.None)] [Guid("854B7690-C1C4-40c4-8059-B4F3450B30D0")] public class Acorn : IAcorn { public Acorn() { } public bool Foo(string moo) { return true; } } Set "Register for COM interop" option for

I followed this article , explaining how to spice up an Internet Explorer COM-Object with jQuery. While the author used Python, I want to do something similar in Powershell. Right now I have this code: function addJQuery ($browser) { $url="https://ajax.googleapis.com/ajax/libs/jquery/1.4.3/jquery.min.js" $document = $browser.document $window = $document.parentWindow $head = @($document.getElementsByTagName("head"))[0] $script = $document.createElement("script") $script.type = "text/javascript" $script.src = $url $head.appendChild($script) while (!$window.jQuery) { sleep -milliseconds 100 }

I've added a callback to an IHTMLElement instance but when the IDispatch::Invoke is called for the event, there are never any arguments (i.e. the pDispParams->cArgs and pDispParams->cNamedArgs are always 0). For example, I add a callback for an onmouseup event. From what I can tell, a callback for this event is supposed to receive a MouseEvent object. Is that correct? If so, what do I need to do to ensure this happens? This is using the MSHTML for IE 6 sp2 (or better) on Windows XP SP2. Events arguments for all DOM events including onmouseup are stored in the parent window's event property (

from time to time, my monitoring application dies for no obvious reason. It seems like "mshtml.HTMLDocument" resource isn't available. Anyone else experienced something similar? Thanks in advance. Error message: 14.04.2011 18:26:37 -> Test 1.2 (Subscriber type requests), error: Unable to cast COM object of type 'System.__ComObject' to interface type 'mshtml.HTMLDocument'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{3050F55F-98B5-11CF-BB82-00AA00BDCE0B}' failed due to the following error: No such interface supported (Exception from