comintern

Linking [chat](https://chat.stackexchange.com/transcript/message/48962737#48962737).

@retailcoder - I was thinking of building a complete mock filesystem to attach when any of the file handling functions were faked. Maybe in its own namespace? Something like: `Fakes.FileSystem.CurDir.Returns("C;\Foo")`...

@retailcoder - It depends. For COM objects, `EasyHook` needs an instance to examine the interface for. IIR, the object itself is always going to be a parameter on the interface...

@bclothier - Maybe, but most likely not. I'm guessing the `rtcCreateObject` is just a thin wrapper around the VBA `CreateObject` function. If RD was hooking that and just newing up...

@bclothier - That's basically what I meant by "I think ultimately it should come down to a design decision as to whether to replace a specific interface member of a...

@ThunderFrame - What about a separate `Proxies` namespace? The use would be something like: `Proxies.Excel.Workbooks("Foo.xlsx").Returns("C:\Test\Bar.xlsx")` That would allow using "non-production" files to run integration tests on.

@PeterMTaylor - Might not be the best identifier to use, but "another party can act for another person" is a great description. What a `Proxy` would do is allow substitution...

@robodude666 - It doesn't even need to be a COM class - it can literally be _any dll_. Would a framework for faking arbitrary `Declare Function`s be useful? That would...

FWIW, I got this error and resolved it by disconnecting from my VPN while device discovery was running. After my TV was found, it works after reconnecting to the VPN.

Great idea. I wouldn't check the number of parameters, but I would check the types. As far as VBA's signature matching is concerned, enumeration members are always `Long`, and I...