# Calling Explicit Interfaces

**URL:** <https://www.ruby-forum.com/t/calling-explicit-interfaces/170126>\
**Category:** IronRuby\
**Created:** [June 12, 2009, 5:22pm UTC](https://www.ruby-forum.com/t/calling-explicit-interfaces/170126 "2009-06-12T17:22:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdeering](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/278dde/32.png) [@mdeering](https://www.ruby-forum.com/u/mdeering)\
**Post date:** [June 12, 2009, 5:22pm UTC](https://www.ruby-forum.com/t/calling-explicit-interfaces/170126/1 "2009-06-12T17:22:12Z")

</div>

Hi,

Is this still a bug i.e. bug #23494.

i’m trying to use cucumber test a WPF app using the WPFAutomation.

there’s an explicit interface implementation of  
System.Windows.Automation.Provider.IInvokeProvider on the  
ButtonAutomationPeer class.

at the moment i’m getting around it by creating a helper object in c#

namespace UIAutomation {  
public class InvokeHelper {  
private readonly IInvokeProvider \_provider;  
public InvokeHelper(IInvokeProvider provider) {  
\_provider = provider;  
}  
public void Invoke(){  
\_provider.Invoke();  
}  
}  
}

and then call in IR:  
ih = InvokeHelper.new bp  
ih.invoke

Is there another way to do this??  
Regads.

---

<div class="post-metadata">

**Author:** ![mdeering](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/278dde/32.png) [@mdeering](https://www.ruby-forum.com/u/mdeering)\
**Post date:** [June 17, 2009, 7:53am UTC](https://www.ruby-forum.com/t/calling-explicit-interfaces/170126/2 "2009-06-17T07:53:22Z")

</div>

Yep, still looks like an issue. Tomas, the bug Michael refers to is a  
RubyForge bug you opened in January:  
[http://rubyforge.org/tracker/index.php?func=detail&aid=23494&group\_id=4359&atid=16798](http://rubyforge.org/tracker/index.php?func=detail&aid=23494&group_id=4359&atid=16798)

So I created a CodePlex bug for it:  
[http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=1594](http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=1594)

In the future, if there is a RubyForge bug that anyone cares about,  
please move it over to CodePlex.

~js