Is it possible to use the surface pro 3 as a dev test device. I tried looking around and there wasn't much information. What I mean by this is you connect your pro 3 to PC and deploy app to the tablet. My guesses are that you cannot but I thought I would get some clarification.
Thanks!
Yes it is possible you have to install remote debugging companents on your Surface Pro 3. And the appropriate one should be x64 version of VS Update 3 for you.
After you have installed the Remote Tools, choose Remote Debugger on the Start screen. The Remote Debugging Configuration appears the first time that you start the remote debugger.
On the Remote Debugging Configuration dialog box:
If the Windows Web Services API is not installed, choose Install
In the Configure Windows Firewall group, choose the networks that you want to allow connections to. Only those networks that the device is currently connected to are enabled. You must choose at least one network.
Choose Configure remote debugging to set the firewall options and start the remote debugger. Open the Visual Studio Remote Debugging Monitor dialog box to give users permissions to the remote tools and to set other advanced options.
The Visual Studio Remote Debugging Monitor dialog box appears. You can give users permissions to the remote tools and set other advanced option from this dialog box. Here you can find information you need.
Choosing the remote device for C# and VB Project:
Select the project name in Solution Explorer and then choose Properties from the shortcut menu.
Select Debug.
Choose Remote Machine from the Target Device list.
Enter the network name of the remote device in the Remote Machine box or choose Find to choose the device from the Select Remote Debugger Connection dialog box.
You start, stop, and navigate a remote debug session the same way you do a local session. Before you start debugging, make sure the Remote Debugging Monitor is running on the remote device.
Then choose Start Debugging on the Debug menu (Keyboard: F5). The project is recompiled, then deployed to and started on the remote device. The debugger suspends execution at breakpoints, and you can step into, over, and out of your code. Choose Stop Debugging to end your debug session and close the remote app.
Source: http://msdn.microsoft.com/en-us/library/windows/apps/hh441469.aspx
Related
I had a Windows 2008 Server which was being used as Application server that has recently been upgraded to Windows 2012 -> Windows Server 2016 -> Windows Server 2019.
All of the applications under IIS work, but one. I am trying to figure out what is wrong. I have installed Visual Studio 2019 Remote Debugging tool on the server and trying to attach to the erroneous project under IIS.
I have the Remote Debugger running
but when I try to attach to remote process the Application pool and user names do not show up in the "Attach to process" window.
Since I can not see the details I can not connect to my application and debug. I am sure that "Show processes from all users" is checked.
I know that if the application does not run on the server it does not show up in this list, but I have called other applications under the site which are running but they don't appear either.
Try run the remote debugger under the different user account:
You can stop the remote debugger and restart it with the account you are using on the local computer.
You can start the remote debugger from the command line with the /allow parameter: msvsmon /allow username#computer
You can add the user to the remote debugger's permissions (in the
remote debugger window, Tools > Permissions).
If you can't use the methods in the preceding steps, you can allow
any user to do remote debugging. In the remote debugger window, go to
the Tools > Options dialog. When you select No Authentication, you
can then check Allow any user to debug. However, you should use this
option only if you have no choice, or if you are on a private
network.
i just installed new Windows 10 version (1703) and now i'm not able to connect any Windows CE device because Windows Mobile Device center 6.1 doesn't run.
I tried to reinstall it but there is no way, the install process stops.
Do i have to downgrade to a previous version of Windows?
Is there a workaround for this situation?
Thanks for your advices
regards
UPDATE: Some good suggestions which seem to work are now at this web page.
https://social.technet.microsoft.com/Forums/office/en-US/9cab3e8e-6cc4-48e4-8ed9-d595bc83f04b/windows-mobile-device-centre
PREVIOUS: I am able to get Windows Mobile Device Center (WMDC) to install, but not fully run. Installing required manually enabling the .NET Framework 3.5 similar to as described at the following web page.
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/how-to-instal-net-framework-35-on-windows-10/450b3ba6-4d19-45ae-840e-78519f36d7a4
After install, you must right click on Start, and then click on Computer Management > Services & Applications > Services. Scroll down to right-click on "Windows Mobile-2003-based device connectivity" to select Properties > Log On. Switch to "Local System account" with checking "Allow service to interact with desktop" then click OK.
On the handheld, tap on Start > Settings > Connections > USB to PC icon, uncheck the “Enable Advanced Network Functionality” checkbox, tap OK, and then connect the cable.
WMDC never shows connected, but ActiveSync on the handheld does, and you can at least open File Explorer on your PC to “browse the contents of the remote device” for transferring files. I am not sure how much this limits RAPI functions.
These Services settings changes must also be re-applied every time you Restart your PC. So this is obviously not a final solution.
I had the same problem.
I just did the following because I had 3.5 net framework :
Click right click on Start, and then click on Computer Management > Services & Applications > Services. Scroll down to right-click on "Windows Mobile-2003-based device connectivity" to select Properties > Log On. Switch to "Local System account" with checking "Allow service to interact with desktop" then click OK.
Restart my computer and it actually works again.
Thanks for sharing!
Try this
Open the command line as an administrator and run these two commands:
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\RapiMgr /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WcesComm /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
After that, reboot your PC/laptop and the Windows Mobile device center should work again.
Follow these steps
Go To Services
Find Windows Mobile-2003-based device connectivity (Something like that)
Select Properties
Log On
Log On As
Select: Local System Account
Go back to General Tab
Select Startup Type: Manual
Click Start
Click Ok
Support Note, 2 June 2017
This worked for me, although not quite perfectly. When I disconnect my device the Device Center should stay up and show Disconnected, but instead it shuts down.
Just in case this helps someone.
Trying to connect VS2008 to WM6.1 device for a legacy project. I have been successful connecting to a WinCE device with just the registry update.
I made the changes as above, the registry updates, services logon to local and interact with desktop. Still couldn't get it to work.
Finally, I disabled the AVG advanced firewall and left the Windows firewall settings as they were and it worked. The firewall is set up so that any apps requiring access through them should cause popups but they didn't.
Can't see anyway to customize the AVG advanced firewall so will leave it off, at least while developing.
Thanks for everyone's help.
Set up:
Host: Windows 10 Enterprise
Guest: Windows 10 Professional
Hypervisor: Hyper-V
Aim:
Create a shared folder between Host and Guest via an internal network to exchange files
How can I achieve this?
Share Files, Folders or Drives Between Host and Hyper-V Virtual Machine
Prerequisites
Make sure you have a Pro or Enterprise version of the Windows OS. The Home version does not provide you with this functionality! From the official documentation:
The virtual machine must have Remote Desktop Services enabled, and run Windows 10, Windows 8.1, Windows Server 2016, or Windows Server 2012 R2 as the guest operating system.
Ensure that Enhanced session mode settings are enabled on the Hyper-V host.
Start Hyper-V Manager, and in the Actions section, select "Hyper-V Settings".
Make sure that enhanced session mode is allowed in the Server section. Then, make sure that the enhanced session mode is available in the User section.
Enable Hyper-V Guest Services for your virtual machine
Right-click on Virtual Machine > Settings. Select the Integration Services in the left-lower corner of the menu. Check Guest Service and click OK.
Steps to share devices with Hyper-v virtual machine:
Start a virtual machine and click Show Options in the pop-up windows.
Or click "Edit Session Settings..." in the Actions panel on the right
It may only appear when you're (able to get) connected to it. If it doesn't appear try Starting and then Connecting to the VM while paying close attention to the panel in the Hyper-V Manager.
View local resources. Then, select the "More..." menu.
From there, you can choose which devices to share. Removable drives are especially useful for file sharing.
Choose to "Save my settings for future connections to this virtual machine".
Click Connect. Drive sharing is now complete, and you will see the shared drive in this PC > Network Locations section of Windows Explorer after using the enhanced session mode to sigh to the VM. You should now be able to copy files from a physical machine and paste them into a virtual machine, and vice versa.
Source (and for more info): Share Files, Folders or Drives Between Host and Hyper-V Virtual Machine
Drawbacks
While this solution is easy and probably works faster then when using internal network, it has its own drawback: the drive is mapped only while there is a connection via the VMConnect client. If you run a vm with some background services or you connect to it via RDP, this approach isn't gonna work. (thanks #sich for pointing this out)
Open Hyper-V Manager
Create a new internal virtual switch (e.g. "Internal Network Connection")
Go to your Virtual Machine and create a new Network Adapter -> choose "Internal Network Connection" as virtual switch
Start the VM
Assign both your host as well as guest an IP address as well as a Subnet mask (IP4, e.g. 192.168.1.1 (host) / 192.168.1.2 (guest) and 255.255.255.0)
Open cmd both on host and guest and check via "ping" if host and guest can reach each other (if this does not work disable/enable the network adapter via the network settings in the control panel, restart...)
If successfull create a folder in the VM (e.g. "VMShare"), right-click on it -> Properties -> Sharing -> Advanced Sharing -> checkmark "Share this folder" -> Permissions -> Allow "Full Control" -> Apply
Now you should be able to reach the folder via the host -> to do so: open Windows Explorer -> enter the path to the guest (\192.168.1.xx...) in the address line -> enter the credentials of the guest (Choose "Other User" - it can be necessary to change the domain therefore enter ".\"[username] and [password])
There is also an easy way for copying via the clipboard:
If you start your VM and go to "View" you can enable "Enhanced Session". If you do it is not possible to drag and drop but to copy and paste.
Enhanced Session
For those who are having trouble getting the "Edit Session Settings..." dialog, I found that I could get to the dialog box by having the guest machine running in windowed mode so that the top menu ("File Action Media Clipboard View Help") was visible, then selecting "File > Exit" (or clicking on the "X" at the top right of the guest machine window).
After that, the dialog would launch from the Hyper-V Manager Actions "Edit Session Settings..." link.
My version is Hyper-V Version: 10.0.22509.1000,I think the best and most convenient way in windows is that configuring the host and the vm in the same subnet,So you can just use the ctrl+c and ctrl+v Seamlessly between host and vm.
My development workstation is running VS2012 Update 1. The OS is Windows 7 Professional Service Pack 1 x64. I have a laptop running Windows 8 onto which I've installed the VS2012 Remote Debugger. I've started msvsmon and it's quietly sitting in the system tray or what passes for it on Windows 8.
I have set up a breakpoint in VS2012 at a location where I need to do some debugging. In VS2012, I click on Debug | Attach to Process... I get the dialog showing the list of processes running on my machine. I change the machine name to the name of the Laptop.
I am having two different problems:
Problem 1:
With Windows Firewall running, VS2012 connects to the remote debugger server. I see the list of the processes running on the Laptop. I choose the one I want to debug and click Attach. I get "Unable to attach to process. The RPC server is not available."
What's going on here?
Problem 2:
I turn off Windows Firewall on my desktop. When I try to connect to the process running on the laptop, it connects and loads all of the symbols. So far so good. Once all of that is finished, I perform the action that would cause my breakpoint to be hit. The process on the remote machine freezes, but so does VS2012. I've sat here as long as 10 minutes waiting with no change. At that point, I kill msvsmon on the remote machine and my program goes away with it, but VS is still locked up.
Any ideas??
I have faced a similar issue in VS 2013 showing the message "Unable to attach to process. The RPC server is not available".
I have resolved this by un-checking the "Use Managed Compatibility Mode" option from Debug > Options and Settings > General Tab.
I am trying to find out a tool to remote control a Motorola MC3190 device running Windows CE 6.0 from a Windows 7 machine.
I have already used Mymobiler with Intermec CN3 device so I tried the answers in this question but I am unable to get it to work.
I have tried both remote.exe.40 and remote.exe.50 in the Mymobiler folder
Using Task Manager on CodeProject mentioned in a question on superuser it seems remote.exe completes execution very quickly (or is crashing silently).
My Start/Programs menu has a MyMobiler entry, so somewhere along the line something seems to have got installed
But when I run Mymobiler on desktop it cannot connect, its icon in system trey remains gray and on mouse hover says Not Connected/
In Proof MyMobiler works for WinCE video the processor is ARM920T-PXA270M while my device has a Marevell, PXA32X-P (link to image) processor could that be the reason?
I have also tried ActiveSync Remote Display from Windows Mobile Developer Power Toys. It installs but at start up it shows an error box with message "The OS or CPU of this device is unknown to this application"
How do I get MyMobiler to work with Motorola MC3190 device running Windows CE 6.0?
Is there any other tool, preferably free, to remote control this device?
EDIT: I came across EveryWAN and found an installer. It works out of box, but it is not available for commercial use and the web-site seems defunct.
PS: I realize the tags are not accurate but I wanted to use something that will attract attention of experts in these similar tags.
I want to clarify one answer to the above which is correct. When using the Microsoft PowerToy activesync remote display, there must be an application on both sides - host(the phone) and remote (the pc). The same is true for MyMobiler.
Install the powertoy on the pc.
For the original Poster: This is what your error message means:
In the case of Activecync Remote display, for newer devices (anything above ARM4 cpus - which means, 2008 and up, or over 200mhz cpus - as a very general guide), the display software cannot detect what type of device you have (it's too new, and not in the list).
For the motorola mc3190, your cpu is arm5 compatible,
and should work with software that has arm4 compliant components. ARD does have arm 4 options. see here...
To Fix it:
You must use file explorer on your pc, and navigate into the application folder: c\Programs...\Windows Mobile Developer...\ActiveSync...\Devices\wce400\armv4t and copy the two files.
While still on the pc, you must then navigate to the Windows folder of the device (with activesync running, OR the phone configured to be seen as a hard disc), use explorer on the PC to navigate to the device.
Vaguely, it will look like this:
Explorer. > Device (such as HTC Phone:)
Or, X:\ , where x is a drive letter.
The first subfolder your select should be Windows. Paste the two files there.
The two files are now copied onto the phone.
At that point, you must, using the phone, load it's file explorer and navigate to that Windows folder on internal memory and manually run cerdisp2.exe that you have now copied there.
With activesync running, and the phone connected to the pc,
You can now run the powertoy active remote display on the pc, and it will communicate with the exe that is running on the phone.
ActiveSync on Xp, or Windows Mobile Device Center on Windows Vista/7/8 must be running for this all to work.
Alternately, the app allows for a networking ip connection instead of activesync, but I have not used it.
When you are done using this app, you must run the kill.exe on the phone, in the windows folder (the second file you copied), to unload the dll that is running.
I can verify this setup works on Xp, Win7 and Win8 - with an Xscale ARM11 528mhz cpu phone.
For MyMobiler, visit their site and get the newest version.
It WILL fix connections that fail, if you have the older version. It's free. They don't support it anymore.
My Mobiler must have activesync running and showing the device connected.
My Mobiler is vastly superior to ActiveSyncRD.
* It will automatically install the pc side app, and push the remote app to the phone, via activesync.
*Further, when activesync is running and anytime you connect the phone, the MyMobiler app will autoload on the phone as well.
That way, whenever you run MyMobiler on the desktop, it will connect to the phone and load right up.
*My Mobiler allows full resolution display, while ARD is limited to 320x400 or similar. 640x800 looks much better.
*MyMobiler also allows full mouse gesture sends, and copy and paste. ARD offers very limited mouse gesture compatability.
MyMobiler also allows IP connections, but they indicate this is slower.
I am now using MyMobiler with Win8 and a touchpad w/ multitouch, and the mouse gestures send very well.
For Windows V/7/8, you might need to run compatability mode on the Mymobiler.exe file. Navigate to the MyMobiler folder, which might be on your desktop. Drill down til you find the exe. Right Click and chose properties. Compatability. Run Compatability Mode for this file, and select XP.
More Notes:
These apps are slow, because USB is slow.
If you enable Fast USB on the phone, it will help speed up any Remote Display noticeably - however Fast USB is unstable, and doesnt work on some configurations. For me, it doesnt work on XP, but does on Win8 - though slightly unstable at times.
On the device: Start> Settings Icon>Connections icon >USB to PC icon. Tick box to enable.
Also, MyMobiler on Win8 will sometimes refuse to connect. Fully unload mymobiler, disconnect the phone, reconnect the phone and watch for activesync to confirm connection. Then reload mymobiler. Sometimes full system reboots are needed, but that's rare.
Windows Mobile Remote Controller app on CodeProject - as linked above, looks excellent. It's for Windows Mobile 7 and 8 - which is fantastic. He provides a rapi enabler to allow use with WinMo 6 / 6.5 devices, which also looks promising.
I've never used MyMobiler, so I can't help there, but how about other options?
Did you look at the Windows Mobile Remote Controller app on CodeProject?
I've had good luck in the past with SOTI's Pocket Controller. It once was free, or had a free version anyway. Not sure if they still do.
Windows CE came with a tool called CERDISP (short for CE Remote Display), which could be built with Platform Builder. I've seen it available as a binary download (like here, for example) on the web before, so no need to actually build it yourself.
I've used MyMobiler (remote.exe.50) on my Windows Mobile 6.5 handheld. It sounds like you got it running. Did you run the MyMobiler client on your Windows 7 box and connect to your handheld by IP address? (Right click on the icon in the Notification Area on Windows 7 and choose "Connect IP...".)
It defaults to the ActiveSync address (169.254.2.1?), so if you're not docked and running ActiveSync, it will fail to connect initially (but manually connecting should work). Misread -- you were able to run the client, but not the server.
You can also elect to run a VNC server on your handheld and use a regular VNC client to connect to it. I've built this one for Windows Mobile 2003 without much of a hitch on Visual Studio 2008. You might have similar luck with Windows Mobile 6.5.
EDIT: If you get the message that reads:
'%s' is not a valid Pocket PC application.
when running the MyMobiler client, then that means that your CPU type (or OS) is incompatible with the application -- so I don't think your PXA32X-P is to blame; especially since the MC3190 appears to be able to run Windows Mobile 6.5 (i.e. the CPU should be "fairly" modern, with support for armv4i). But since you haven't mentioned an error that looks like that, I'd suspect that your build of Windows CE 6.0 doesn't contain all the required dependencies.
The first thing I'd check is if all of the dependencies of MyMobiler are present in your build of Windows CE 6. Windows CE is highly customizable; as such, not all software components will be the same across different builds of Windows CE. MyMobiler is built targeting Windows Mobile, not Windows CE, so there's a good chance that your build of Windows CE on the MC3190 doesn't have what's required, while the video you linked does.
With regards to the ActiveSync Remote Display Power Toy, the message that you received sounds like the desktop application didn't know what version to deploy to your device.
Per readme.txt in the ActiveSync Remote Display package:
If you see error message "The OS or CPU of this device is unknown to
this application", it usually means the CPU type of the current
device, typically a Windows CE device, is not recognized by this tool.
The workaround is
1. Find the CPU type of the device (from the manual or the manufacturer).
2. Copy \Devices\wce400\\cerdisp2.exe to the \windows folder of the device.
3. Run "cerhost2.exe -m" on the desktop/laptop.
4. Run cerdisp2.exe on the device.
5. When the remote display is no longer needed, terminate cerdisp2.exe on the device.
You should be able to choose the armv4t version; if not, use the armv4 version.