Recently, when debugging with Fiddler and Visual Studio 2015, I got a lot of requests in the Fiddler list, that weren’t relevant for the work I wanted to accomplish. Actually, they were making a mess, preventing me from finding the desired requests to inspect.
I am talking about the /vshub/… requests, and I mean really a lot of them, like dozens in a second, e.g.:
Czytaj dalej Fiddler full of /vshub/ requests
recently I encountered a problem trying to start a Windows Phone Emulator from within Visual Studio 2012. In a WP8 project, starting a debugging session effected in loading the emulator box, but then right away stating the following:
The Windows Phone Emulator wasn’t able to connect to the Windows Phone operating system:
The emulator couldn’t determine the host IP address, which is used to communicate with the guest virtual machine.
Some functionality may be disabled.
The WP8 app did not start, all I could see was the main tiled page of the emulated phone. Additionally, Visual Studio reported an error: „Invalid pointer„.
Some sources on the web state that this might me caused by an interference between e.g. VPN client software and the emulator network usage. It was not quite what I would want to do, and luckily I found another solution:
- Started Hyper-V manager
- Virtual Switch Manager
- Removed the „Windows Phone Emulator Internal Switch” from the list, and applied the changes.
Starting the emulator afterwards required an elevation of privileges for the system in order to create the switch again, this time without any conflits.
Et voilá, emulator does not seem to have connectivity problems anymore, the debugging works as it should.
Hope it helps,
Hi there, just a quick one this time.
Today I struggled for some time with a Facebook app, which was meant to display as a page tab. A basic functionality: take an external URL and display it within the page tab.
The problem was that the page was not appearing, although the server was publicly available and pasting the URL in a browser worked as expected. After some research, it came out that the URL using commas and semicolons in querystring has to be encoded, otherwise Facebook won’t like it.
Thus, changing from http(s)://www.example.com/page.html?a=1,2&b=3;4
seems to solve the problem and the page gets displayed.
Hope this helps,