I haven't any other working ways of communication with WindowsOnDevices community (given on site https://ms-iot.github.io/content/ContactUs.htm) so I'm trying to ask here.
I got Intel Galileo from Microsoft IoT program, connection is working, I can ping it, watch files on SD card, do something via Telnet, etc. Microsoft gives SDK for Galileo in Visual Studio Express 2013. I installed it and configure as they told on https://ms-iot.github.io/content/, so I wanted to launch "Hello world" blinking LED app from their site, debugging over ethernet. I press F5 or click Debug in Visual Studio, it writes me "Operation is taking longer than expected" so I waited for 5, 10 and 15 minutes but nothing happend. Only in console "1>------ Deploy started: Project: Blink, Configuration: Debug Win32 ------"
I turned off all firewalls, it doesn't helped. When I kill remote debugger app (msvsmon.exe) on Galileo, it doesn't starts, so it can see this app on device. What could be wrong?
If you didn't use the default name for your Galileo ("mygalileo"), you'll have to enter your board's name in the Project Properties.
Related
Been trying to deploy one of my projects onto the Microsoft HoloLens 1 via USB. For some reason, I keep getting an error about remote authentication: "DEP6957: Failed to connect to device '127.0.0.1' using Universal Authentication. Please verify the correct remote authentication mode.. etc."
I'm using Bootcamp on a Macbook Pro + HoloLens 1 with Visual Studio 2019.
Things I've done:
Developer Settings on Both HoloLens1 and Laptop.
Clean/Rebuild solution.
Pair HoloLens to Laptop with the Microsoft HoloLens desktop app.
Selected x86 & Debug with deploy to DEVICE.
Both devices on same Wifi network.
HoloLens connected via usb.
Really hoping someone can help! I've gone through most of the forums online and they all say more or less the same things which I've already done. I've attached some screenshots as well.
UPDATE: Installed the USB Device connectivity on Visual Studio and am still getting the same errors.
We think this issue may happen due to the lack of USB Device connectivity component in Visual Studio and the following steps worth trying for you.
Check if the component USB Device connectivity has been installed for your VS. If not installed, you can install it with Visual Studio Installer.
Unpair all devices in Setting from your HoloLens.
Deploy your project to your device, the first time Visual Studio deploys it, you will be prompted for a PIN. Follow the Pairing your device instructions.
I have been facing the same issue as asked in this other post
Visual Studio 2015 Windows Phone Emulator not deploying
but the solution worked here is not working for me.
Windows 10 pro upgraded from home version
Visual Studio 2015
Apache Cordova "Sample" app.
In Emulator it is showing as "Starting
in the behind "Hyper-V" "Summary" it is visible but if double click the the Hyper-V "instance" it is not visible there but only in "Summary"
What am I missing here?
For the developer sake and investment, MS must make sure that the solutions are tested everywhere before releasing them.
This link will direct you to print screen of the error. https://prnt.sc/cykrgg
in the VS output we get the following last message.
My OS is 64 bit.
2>The build configuration was changed to x86 for x86-based emulator deployment.
could this be impact of 64 to 86 bit version difference or anything else?
I have Norton antivirus
I am getting
Hyper-v administrator pop up every time I try to run the app.
This case is resolved by Microsoft Support Team over a Ticket and Rohit, support engg from MS did really helped me a lot.
The reason why it was not coming up.....
My machine has a AdWareAntiVirus from Lavasoft by Name WebCompanion that was not allowing it work.
I removed it then it started working.
if any body have any problem with VS 2015 Emulator definitely focus on the Antivirus and include the Emulator XDE into exception list and also include in Firewall.
Thanks,
Ekambar
I'm developing a UWP app for Windows 10 Phone. Since some days when I try to deploy the app from within Visual Studio I get asked for a PIN in order to connect to the device
In the phone settings I can trigger pairing so a new PIN is generated for me. But when I enter that PIN, a new dialog appears telling that the PIN was wrong:
If I press 'Cancel' then the deployment is interrupted with an error message:
1>Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
It's strange but some days ago I was not asked for the PIN when I deployed the app. :-( So currently the only option I have is deploy via the web portal. This works but it's enormously slow :-(
Can someone tell me how to solve the problem or what PIN should I enter in order to achieve the deployment?
I had this problem today, closing visual studio and restarting IpOverUSB service fixed this issue for me.
You might want to take a look at Ricardo Pieper Question he has listed all the things he tried to do and all the things that might work.
It looks like the problem was caused by the fact that I'm developing inside a virtual machine (VMWare Fusion on Mac). After setting up the development ebvironment on a PC the deployment works fine.
I can even debug the app running on the phone from inside Visual Studio.
Here's a solution which worked for me:
I had the same problem on my Macbook running VMWare Fusion and trying to debug on my Lumia 950 phone. I was nearly giving up, then I tried using the free VirtualBox and with a virtual USB 3.0 port (which requires the VB extension pack). And it worked!!
Here's my setup:
VirtualBox 5.0.14
VB Extension Pack
Win 10 Development VM from Microsoft – the VirtualBox variant, Build 201601: https://dev.windows.com/en-us/downloads/virtual-machines
Lumia 950 with Windows 10 Mobile 10.0.10586.29
In the VM, I configured to use the USB 3.0 port, since with USB 1.x the phone device driver could not be installed by Windows 10.
The VM contains Visual Studio 2015; I created a UWP JavaScript application and ran it with "Debug" on the connected Lumia device.
Had to go to the Developer options on the device.
Switch back to "Windows Store Apps" option, and then back to "Developer Mode"
I've written a Windows driver sample (WDM) with Visual Studio but I'm encountering issues when trying to debug it. The target is running in a Virtual Machine (VMware)
I've followed the documentation (http://msdn.microsoft.com/en-us/library/windows/hardware/hh698272(v=vs.85).aspx) to configure everything.
It's compiling fine but there are problems when debugging.
I have tried various configurations and have different problems on each.
Visual Studio 2013 Preview on Win7 (host) / Win8.1 Preview (target) - VMware
It seems the debugger isn't working properly. Indeed it's like if nothing was loaded, the Modules Window is empty, when I click on "Break all" nothing is happening. As you can see in the logs, the debugger session isn't created.
Screenshot:
Logs: http://pastebin.com/DfVzGR4Z
Visual Studio 2012 on Win7 (host) / Win8 (target) - VMware
It's working correctly at the first try but if I stop the debugger to modify the driver, it'll freeze the VM. I'll then have to restart the VM, Visual Studio and kill the process ntkd.exe because otherwise I have these errors:
Failure to create process instance prevents debugging
Unable to start (null), Error 80004005. (Unspecified error)
Followed by a crash of VS (Event Name: CLR20r3)
I've tried with other samples downloaded from the MSDN but it's the same problem.
I've been stuck on these issues for weeks and I'm starting to desperate, so any help would be appreciate. I haven't tried WinDDK but since VS has everything needed, I don't see why I couldn't use it normally.
I recommend to forget using Visual Studio for driver development/debugging because, on my opinion, is not solid enough.
But targetting the debugging process, it is better to install VisualDDK and then launch vmmon/vmmon64.
In the installed application you will find a folder named "target" with an application named DDKLaunchMonitor.exe, install it in the virtual machine (it will create a boot menu option to activate kernel debugging)
When you want to debug your driver, launch vmmon, activate the option to launch windbg at vm startup, start your vm and when windows boots it will load windbg and attach to the vm.
The install your driver as desired and learn windbg.
I know this answer does not solve you problem with VS but using windbg directly is faster and better.
I was having a similar problem with: Visual Studio 2015 Community Edition, Windows 10 host, Windows 10 target, VirtualBox with host only network.
Provisioning and remote driver deployment worked, but the debugger would not connect.
Edit: In the last step of provisioning in VS2015 the Host IP can be selected. The manual method below is an alternative.
The manual setup guide for kernel mode debugging says to run the following:
bcdedit /debug on
bcdedit /dbgsettings net hostip:w.x.y.z port:n
Visual Studio automatically runs these during the provisioning process. Notice the hostip parameter - this has to be the address of the connecting machine (the one with the debugger) on the interface it uses to connect to the target. Visual Studio may set this incorrectly if you have multiple network interfaces. In my case the VirtualBox host only network created the extra network interface.
Provision the target machine in VS, if you haven't already. Then run the two bcdedit commands above and reboot the target machine. After this, the debugger should connect properly.
I came across the same problem. The windbg connection is hang. I found there is something wrong in my configuration for Kernel mode debugger settings( Visual studio 2012 Driver->test->Configuration). I set the port simply com1. Actually, it should be \.\pipe\com_1.Then it works
In your case, there maybe other configuration problems. You can check through the points on webpage http://www.codeproject.com/Tips/545835/Kernel-Mode-Debugging-in-a-VM-using-Visual-Studio.
To build my driver i used VisualDDK in visual studio 2008. In the beginning i start debugging using my computer and virtualBox machine but when i launch the debugging process in visual studio, my virtual machine did not show me the external ip address(normally should show me 192.168.1.102 and 10.0.1.15 in DDKLauncherMonitor but it show me only 10.0.1.15 ).
I stopped using virtual machine and i decide to use real computer. In the second computer i launched DDKLauncherMonitor. And i start debugging from my first computer. I received Udp package in my second machine and also the driver.sys. But when i tried to load the driver from visual studio(First computer) nothing work. Plus this, in the second machine tell me "Windows required digitally signed driver".
There is same one meet this kind of problem and he/she can help.
Can you go into more details when you say "nothing works"? It's possible that your debugger is not set up properly.
This is kind of a pseudo-answer since I'm not overly aware of VisualDDK, but have you considered trying the standard Microsoft debugging tools like WinDbg? If you can acquire Visual Studio 2012 or 2013 Preview, all of the build and debug tools are integrated into the IDE and you will get full support from Microsoft with any problems you may encounter.
As for your second issue, it sounds like you're building a driver and not signing it. Is your target PC 64-bit? What operating system is it? The 64-bit Windows platform requires signed drivers for installation, but this can be disabled.
You can disable the driver signing requirement using the F8 menu when booting your PC; this should fix your "digitally signed driver required" problem, but needs to be done for each reboot.
Another option would be to add a post-build step or some sort of scripted execution of the Microsoft signing tools (Inf2cat, SignTool) to sign your driver with your company's certificate.