1

Closed

method not found exception when using new PairWithVirtualControllerExclusive method

description

I'm trying to use the new user.PairWithVirtualcontrollerExclusive method but when I call it a method not found exception is thrown. In the past this was just some out of dated assemblies, but I've rebuilt the whole project and I'm still seeing this. Everything else I was using before is still working.
Closed May 13, 2015 at 9:06 PM by amccalib

comments

besund wrote Jan 2, 2015 at 6:28 PM

Could you post a little more information about your situation? Specifically, a stack trace, the XDK version of the computer running XboxConsole, and the Kit's flash version.

Since everything else is working, my initial thought is that you are running XboxConsole with an older XDK installed. This would mean that you are using an older adapter. Since the base functionality for PairWithVirtualControllerExclusive was added in the November XDK, only the November2014 adapter supports it. You have to at least have the November XDK installed for XboxConsole to use it.

besund wrote Jan 2, 2015 at 10:26 PM

Looking more into this, it looks like the issue has to do with the way the ManagedXTF dependency is handled during build.

Each adapter embeds its own ManagedXTF dlls so that it can load the appropriate one at run time. What is happening is that each adapter is copying it's own ManagedXTF dlls into the output folder, overriding each other with the last alphabetically being copied last. If these dlls exist locally in the folder that XboxConsole is run from, than the assembly resolver will load the local dlls, instead of loading the embedded dlls from the adapter.

There are two options to workaround this. First is you can remove the local Microsoft.Xbox.Xtf* dlls from the output folder, or make sure that if/when you copy the XboxConsole dlls that those dlls are not copied as well. Second, you can set the Copy Local property to false on all those dlls in each adapter to prevent the dlls from being copied in the first place.

Urrioux wrote Jan 5, 2015 at 3:50 PM

Great thanks for looking into this! I'm going to set it up so that the adapters don't copy their xtf refs to the output folder. Any chance you guys could do this for future drops?

vanovy wrote Jan 6, 2015 at 7:02 PM

We will fix this in the next source code drop.

besund wrote Jan 21, 2015 at 5:42 PM

The latest release 2.0.50121.0 should fix this

besund wrote Jan 21, 2015 at 5:45 PM

Resolved with Change set 38140

wrote May 13, 2015 at 9:06 PM