Windows Mobile device not connecting to VS2008 using CoreCon/RDB2008 - debugging

I am trying to connect a Windows Mobile 5.0 device with Visual Studio 2008 using Corecon (tried all processor architecture files available inside wce400 folder) and RDB2008, but it won't connect. Here is the device details page:
Does anyone have any idea what could be wrong here? I suspect a mix-up of Device OS, architecture and SDK. Appreciate any effort or help on this. Thanks.

Remote debug within VS2008 for a Windows Mobile device needs a valid IP connection with the debug ports (5655) opened (if a firewall is active).
First try to start a debug session with a simple .NET Compact Framework application (a C# SmartDevice project) and the device is connected via USB ActiveSync/WindowsMobileDeviceCenter. If that does not work, you are in trouble. Does the device connect to Windows Mobile Device Center? Try Start>Settings>Connections>USBtoPC setting change on the device.
If you can 'debug' using an USB connection but not using WiFi, check subnet and ports and Internet connection setting for Wireless Card on the device. Can you ping the device from the VS2008 PC? Can you ping the VS2008 PC from the device (vxUtils ping)? Is the debug port opened on the device after RDB2008.exe started and installed (see my NetStat for Windows Mobile)?
You may try a network trace on the VS2008 PC to see what happens on port 5655. Or even a network trace on the device (MS powertoys NetAnalyze).
I assume you followed this

Related

How to deploy a UWP to a Galaxy TabPro S with windows 10 OS?

I'm trying to deploy a UWP app from my Alienware 18, Laptop with Windows 10, version 1803 to a Tablet Galaxy TabPro S with Windows 10 version 1803 as well.
I had activated developer mode on the device target and the USB device discovery option as well.
First I tried connecting a USB Cable from my laptop to the tablet which has a USB-C port.
But My laptop doesn't even find it.
What I want is to find a way to deploy a UWP from my laptop to the tablet, I made some research and I found out that, only HoloLens and Windows Phone 10, are findable using USB Connection.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
I would appreciate details because I tried to follow remote deploying but I haven't been able to successfully find the tablet.
The Windows 10 on your tablet, just like on your development machine, supports remotely debugging over the network rather than over USB. Make sure both machines are in developer mode, with the other machine also having Device Discovery turned on as described here. Both should connect to your WiFi as a private network. After that it should be as simple as configuring your project to deploy to the other machine, rather than locally, as described here and here. Don't forget to pair them with a PIN.
If you host a web API on your development machine, configure your firewall as described here.
Use remote debugging over at https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging?view=vs-2017
Make sure you follow the instructions, sometimes remote debugging is barred by firewall so check that.
Alternative right click your main project, go to store then click create packages for sideloading and then send the package over at your Samsung device.
So what step should I follow to successfully remote debug my app to a windows 10 Tablet.
To run a UWP app on a remote machine, you must attach to it using the Remote Tools for Visual Studio.
In some scenarios, the remote tools are automatically installed when you deploy to a remote device. For example,
For Windows 10 PCs running Creators Update and later versions, remote tools will be installed automatically.
Then, your remote device and the Visual Studio computer must be connected over a network or connected directly through a USB or Ethernet cable. Debugging over the internet is not supported.
After that, you need to configure the Visual Studio project for remote debugging. In the properties of the project, select the Debug and choose the Remote Machine from the Target Device list. In general, I will input the remote machine's IP address, you could choose Find to choose the device from the Select Remote Debugger Connection dialog box.
Next step, please move to your Tablet, you need to Set up the remote debugger. You must have administrative permissions on the remote computer. Then, open the Start menu and search for Remote Debugger. If you could find it, just start it normally. If you cannot find it, you need to install it Remote Tools manually. See this link to Download and Install the remote tools. Once the Remote Debugger started, you could do some configurations. After that, you could choose Start Debugging on the Debug menu (Keyboard: F5). The project is recompiled, then deployed to and started on the remote device. Please read Run UWP apps on a remote machine in Visual Studio for more information.

Visual Studio Android Emulator internet connection

Android emulators cannot connect to internet when using WiFi on host computer. The host is a Macbook pro and the development environment is Visual Studio 2015 running inside a Windows 10 VM using Parallels. When I connect an ethernet cable to the Macbook the Android emulator can connect to the internet and load websites, but when using WiFi on the host it cannot connect. Has anyone else had this issue?
Check network adapters in virtual machine. You probably have some from Oracle Virtual box or other
I put this to work in a nested virtualization environment, but my host is a Windows Server 2016 machine:
Physical machine (WinServer2016) -> VM (WinServer2016) -> VS Emulator for Android
I had to execute the following command in my host:
Set-VMNetworkAdapter -VMName $vmName -MacAddressSpoofing on
I think that if you enable MAC address spoofing on your Macbook pro this will work.
The issue was with Wifi. If the Mac host was connected to the internet via Wifi then the emulators running inside of the Windows VM could not access the internet. Once I switched to LAN connection the emulators were able to connect to the web.

USB Debugging in Windows CE?

How to debug a windows CE device using USB?. Is there any tool available to debug windows CE devices through usb?
As far as I know, you need TCP/Activesync to debug a winCe device.
From visual studio/Platform builder, you can select your SDK, and the corresponding device. The device may already be connected to your network, in which case, you can provide its IP address. If not, you can connect it to your PC using a USB cable. After connection, it seems to share your PC's internet connection and it will be assigned an IP.
You can set visual studio to auto-detect your device without providing a fixed IP only.
Visual studio>Tools>Options>Device Tools>Devices gives you the above mentioned settings.
Anyway, your device must be connected to your network. Though I am not sure, you might be able to fiddle with your windows settings such that when you connect your device to the USB, your PC will assign it an IP and use 'Microsoft Loopback Adapter' as the network adapter. In this case, your device will not be visible to the rest of the network, but only to you.

How to deploy and debug wdk 8 kernel mode driver

I’m trying to set up automatic driver deployment and debugging to test a win 8.1 driver from Visual Studio 2013.
Host machine:
Win 7
VS2013
Target Machine:
Win 8.1
My host machine is set up with 2 network cards, 1 which connects to the corporate network and one spare. The target machine also has a network adapter.
My question is: is it possible to set up automatic deployment and debugging of drivers in Visual studio 2013 by connecting the host and target via a LAN whilst still being connected to the corporate domain and if not, is there a way of debugging wdk drivers on a target pc outside of visual studio, maybe via another application?
The documentation I found here only makes it seem possible by connecting to the same domain name or workgroup.
link to documentation
Many Thanks
Yes you can set up automatic deployment of the driver as well as getting visual studio to do the provisioning of the target pc over a local network as well as being connected to a corporate domain.
Admin rights are needed on the target
An extra ethernet card is needed in the host
All networks connections on the target are open with printer and file sharing options enabled
The ip and name of the target are listed in system32/etc/host in the host PC
A switch is needed and DHCP setting are enable with automatic IP
A good place to start:
https://msdn.microsoft.com/en-us/library/windows/hardware/gg507680.aspx
EDIT:
Basically, this was a nightmare and started dropping its connection. I reverted back to using WinDBG using:
custom scripts to copy everything over to USB
devcon to automactially load the driver
WinDBG to autoload appropriate settings on startup and load source files in to debug

How to debug windows phone 8 app in remote system?

I am working on project. I have taken remote system. My problem is that Visual studio and windows phone 8 device located in remote place. Windows phone 8 is connected in remote server. All sources and devices are located in remote server. I need to test and debug the app. How can i see the device screen? I want to control the device using remote server. Any software or method to take control the phone in PC?
In other words, I want to control or display the screen of windows phone 8 device on PC.
Any idea should help me a lot.
Thanks in advance.
As there is not a way to interact with a physical Windows phone 8 remotely yet (unless you are a Microsoft employee with special access to private builds of the phone), I'd suggest that the remote site set up a machine configured with Windows 8.1, Hyper-V, Visual Studio for Windows Phone, and the emulators. You can use Remote Desktop to gain access to the machine and test and debug the application through the emulators.
Or, of course, the best would be if you could just gain access to the source code for the application and do the testing locally. Depending on the resources required by the application, you may need to create a LAN to LAN VPN in which all traffic would route through the remote site.

Resources