Troubleshooting common issues with XAML Spy. Contact us when your issue is not listed.
The installer exits with error 2885. This error indicates you are trying to install XAML Spy on an unsupported operating system. You need Windows Vista, 7 or 8. If you are installing XAML Spy on a Windows Server, you need to have at least Windows Server 2008 R2.
Older operating systems (including Windows XP) are not supported.
The XAML Spy installer fails with a message that it is unable to start the XamlSpyService. Additional details about the error can be found in the Event Viewer application log. There are various reasons why the service may fail to start. Check the options below.
Error: incorrect file permissions
The XamlSpyService logs on as the NETWORK SERVICE account, and it is most likely this account does not have the appropiate file access permissions. Be aware that service permission issues are unrelated to the current interactive user. Please verify NETWORK SERVICE has the following file permissions:
Error: The requested address is not valid in its context
The Event Viewer displays a socket error with message The requested address is not valid in its context. The XAML Spy Services tries to bind to an IP address that is not valid for your machine. This is most likely caused by an invalid XAML Spy configuration file from a previous installation. You'll need to manually remove the config file and re-try the installer. The XamlSpy.config file is located at C:\ProgramData\First Floor Software\XAML Spy, that is ProgramData, not Program Files(!).
Please contact us if above doesn't resolve the issue. If possible include the error details found in the Event Viewer application log.
The reasons for this error may vary. To see the actual error you'll need to run the setup using msiexec and with logging enabled. Follow the steps below:
Possible causes of premature setup exits.
This error occurs when launching XAML Spy and the XAML Spy service is not running. Either this happens because the XAML Spy service has been stopped, or has not started yet. The XAML Spy service is configured to run when the OS is starting, but does so in a delayed manner to ensure the OS is booted as fast as possible. It may take a couple of minutes after the OS has booted, for delayed started services to actually start.
Resolution: either wait for the XAML Spy service to start when you just rebooted your machine or manually start the service by navigating to the XAML Spy service settings (settings > xaml spy service) and selecting the restart service button.
This error indicates that XAML Spy found a host at the remote address, but is unable to connect to the remote port.
An attempt to connect to the XAML Spy service is already in progress. This message occurs when you manually select the reconnect button. When connecting to the XAML Spy service takes a long time, this usually indicates that the connection attempt will eventually time out.
Resolution: check the suggestions at The connected party did not properly respond after a period of time.
It may take at least 10 seconds up to a couple of minutes for this time out error to occur. The underlying network is unable to reach the remote host and a timeout error (socket error 10060) occurs.
See also the suggestions at An attempt was made to access a socket in a way forbidden by its access permissions.
This error occurs when running a Windows Phone app in a Windows Phone 7.x emulator where you try to connect to localhost (127.0.0.1).
Resolution: ensure the XAML Spy service is listening on a public facing IP address and change the connection settings so that the app connects to this address.
You are trying to connect a Windows Store app to a public facing IP address, which requires the capability privateNetworkClientServer.
Resolution: enable the capability privateNetworkClientServer for your app. Open Package.appxmanifest in Visual Studio, select the Capabilities tab and check the option Private Networks (Client & Server).
This error does not occur when connecting Windows Store apps to localhost.
Either no or an invalid password has been provided. A valid password is required in order to connect to the XAML Spy service. You can lookup the password in the XAML Spy service settings (settings > xaml spy service).
Selecting the context menu option Enable XAML Spy for your project, shows the following warning message in the XAML Spy Power Tools output pane: WARNING: environment variable 'XamlSpyInstallPath' not set. Is XAML Spy installed?
The XamlSpyInstallPath environment variable is not set, which causes the XAML Spy targets import condition to evaluate to false. XAML Spy will be not enabled. This warning occurs when XAML Spy is not installed (properly), or an older version of XAML Spy is installed.
Resolution: make sure you have installed XAML Spy 1.2 or higher.
With XAML Spy integration enabled for a Windows Store app, running unit tests in the Visual Studio Test Explorer will fail. In Visual Studio 2012 the following error occurs: Failed to activate Windows Store app unit test executor. Error: The remote procedure call failed. In Visual Studio 2013 a System.AccessViolationException (Attempted to read or write protected memory) is thrown.
The Windows Store unit test runner doesn't correctly handle custom types in XAML. XAML Spy does insert a number of custom attached dependency properties to all XAML resources. A related issue is reported on StackOverflow.
Resolution: disable XAML Spy integration before running Windows Store unit tests.
When building a WPF project the following build error occurs:
The build error occurs when XAML Spy is enabled for a class library, but not for the main app project referencing this class library project.
Resolution: enable XAML Spy for the main app project as well.
The Windows 8 operation system suspends Windows Store apps automatically when they are no longer visible and active. A suspended app loses its connection with XAML Spy.
Resolution: either debug your app with Visual Studio or keep your app visible (on a 2nd monitor) to prevent suspension.
The WebView control in Windows Store 8.1 apps no longer responds to mouse moves and clicks when XAML Spy is enabled for the app. The overlay popup that XAML Spy creates to render visual cues, prevents the WebView control from receiving mouse events.
Workaround: you can toggle the visibility of all XAML Spy visual cues by pressing CTRL-Shift-X. This closes the overlay popup and enables mouse interaction with the WebView control. Press CTRL-Shift-X again to show the popup.