简体   繁体   English

无法将UWP应用部署到Raspberry Pi 3

[英]Cannot deploy UWP app to raspberry pi 3

I'm getting an error : 我遇到一个错误:

Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named 'minwinpc'. 错误:无法连接到名为“ minwinpc”的Microsoft Visual Studio远程调试器。 The Visual Studio 2017 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. Visual Studio 2017远程调试器(MSVSMON.EXE)似乎没有在远程计算机上运行。 This may be because a firewall is preventing communication to the remote computer. 这可能是因为防火墙阻止了与远程计算机的通信。 Please see Help for assistance on configuring remote debugging. 请参阅帮助以获取有关配置远程调试的帮助。

I'm trying to deploy an app to my RPI 3 running Windows 10 IoT Core v.10.0.16299.15. 我正在尝试将应用程序部署到运行Windows 10 IoT核心版v.10.0.16299.15的RPI 3。

I've tried: 我试过了:

  • Reinstalling Visual Studio 2017 重新安装Visual Studio 2017
  • Installing Visual Studio 2017 Remote Debugger. 安装Visual Studio 2017远程调试器
  • Restarting the VS. 重新启动VS。

I noticed that Visual Studio 2015 remoter debugger is running on raspberry pi and it has 192.168.0.6:8116 as a remote machine name while in VS2017, rpi's address is 192.168.0.6:4002. 我注意到Visual Studio 2015远程调试器正在树莓派上运行,并且它具有192.168.0.6:8116作为远程计算机名称,而在VS2017中,rpi的地址是192.168.0.6:4002。 Why are they different? 他们为什么不同? Can someone help me? 有人能帮我吗?

As Martin & Belekz mentioned,you can check the configuration of target device and firewall setting.And more,I want to add that,please note the configuration of Authentication Mode .You should set it as " Universal(Unencrypted Protocol) ".Use the mode whenever you are deploying to a remote device. 正如Martin&Belekz提到的,您可以检查目标设备的配置和防火墙设置。此外,我想补充一点,请注意身份验证模式的配置。应将其设置为“ Universal(Unencrypted Protocol) ”。当您部署到远程设备时,请选择“模式”。 Currently, this is for IoT devices, Xbox devices, and HoloLens devices, as well as Creators Update or newer PCs. 当前,这适用于IoT设备,Xbox设备和HoloLens设备以及Creators Update或更新的PC。 在此处输入图片说明

Look at my post here i have the same problem and i tried several things, but only after i done this i can deploy remotely to pi again: 这里查看我的帖子,我遇到同样的问题,我尝试了几件事,但是只有完成此操作后,我才能再次远程部署到pi:

  • Uninstall old 16299 SDK and download new 16299 SDK from here 卸载旧的16299 SDK并从此处下载新的16299 SDK
  • Repair VS from VSInstaller 从VSInstaller修复VS
  • run sfc /scannow 运行sfc / scannow

Also make sure you're using Universal authentication mode and type the ip without port number (or even using 'minwinpc' is enough) 还要确保您使用的是通用身份验证模式,并键入不带端口号的ip(甚至使用'minwinpc'就足够了)

hope this helps 希望这可以帮助

You can configure the remote debugger's IP address and port to point to the correct endpoint of your Remote debugger. 您可以将远程调试器的IP地址和端口配置为指向远程调试器的正确端点。

Right-click the UWP app project, choose Properties , and in Debug tab you will see Start options with Target device which should be set to Remote Machine and below you can manually enter the Remote debugger's IP address and port into the Remote Machine field ( 192.168.0.6:8116 in your case). 右键单击UWP应用程序项目,选择“ Properties ,然后在“ Debug选项卡中,将看到“ 目标设备的 Start options ,应将其设置为“ 远程机器” ,在下面,您可以在“ 远程机器”字段中手动输入远程调试器的IP地址和端口( 192.168.0.6:8116 )。 You should include the 8116 port in the Remote Machine field as well. 您还应该在“ 远程计算机”字段中包括8116端口

This should make Visual Studio connect to the Remote debugger instead of the RPI itself. 这应该使Visual Studio连接到远程调试器,而不是RPI本身。

Also try to turn off the firewall to verify if it does not interfere with the connection. 另外,请尝试关闭防火墙,以验证它是否不会干扰连接。

I never deployed software from VS to a RPi using an port in the IP address before. 我以前从未使用IP地址中的端口将软件从VS部署到RPi。 So maybe you are doing something special, or I'm doing something basic, but; 所以也许您在做一些特别的事情,或者我在做一些基本的事情,但是;

  1. dubble check if you need to assign a port. dubble检查是否需要分配端口。
  2. Start Windows 10 IoT Core Dashboard and check if the Pi is visible in your network. 启动Windows 10 IoT核心控制台,并检查Pi在您的网络中是否可见。

    --> If not, try to ping to your Pi, using the CMD ->如果没有,请尝试使用CMD ping您的Pi

     ping 192.168.0.6 

    --> If the ping fails, check your IP address of your Pi with a physical monitor. ->如果无法ping通,请使用物理监视器检查您的Pi的IP地址。

  3. Check the address in the build properties according to the steps above. 根据上述步骤检查构建属性中的地址。

    打印屏幕属性

Hope this helps! 希望这可以帮助!

i have see same problem in my laptop. 我在笔记本电脑中遇到了同样的问题。 i solve this problem by following steps.. 我通过以下步骤解决了这个问题。

first of all can you install Windows 10 IOT SDK in your .net? 首先,您可以在.net中安装Windows 10 IOT SDK吗?

if no then first of all download and install. 如果否,则首先下载并安装。 otherwise update vs 2017. 否则更新与2017年。

when install vs 2017 then automatically install iot sdk. 在安装vs 2017时,然后自动安装IoT SDK。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM