无法使用通用身份验证连接到设备“192.168.1.17" [英] Failed to connect to device '192.168.1.17' using Universal Authentication
问题描述
我尝试从 Visual Studio 2015 将 WPA 应用程序部署到 Windows IoT Core 10.
当我尝试部署时，出现错误:
无法使用通用身份验证连接到设备192.168.1.17".请验证在中指定了正确的远程身份验证模式项目调试设置.0x89740016:来自 HRESULT 的异常:0x89740016
如果我将身份验证模式更改为无，则会出现错误:
无法连接到名为minwinpc"的 Microsoft Visual Studio 远程调试器.Visual Studio 2015 远程调试器 (MSVSMON.EXE) 似乎未在远程计算机上运行.这可能是因为防火墙阻止了与远程计算机的通信.请参阅帮助以获取有关配置远程调试的帮助.
这是配置页面:
如果我尝试从 Windows 设备门户 部署 CurrencyExchange_1.0.9.0_ARM_Debug.appx，我收到错误:
失败原因:Windows 无法安装包e0c3666e-088b-4aed-8c79-8f7ddb1541fa_1.0.9.0_arm__ya2k1rc7yvhh6因为这个包依赖于一个找不到的框架.提供由微软发布的框架Microsoft.NET.CoreRuntime.1.0"CN=微软公司，O=微软公司，L=雷德蒙德，S=Washington, C=US"，具有中性或 ARM 处理器架构和最低版本 1.0.23819.0，连同这个包一起安装.这当前名称为Microsoft.NET.CoreRuntime.1.0"的框架安装的是:{} 失败文本:包更新失败、依赖项或冲突验证.(0x80073cf3)
这是Device Portal的截图:
如果我尝试在 Device Portal 中启用调试，我收到错误:
未能启动 Visual Studio 远程调试器.远程调试器需要复制到设备中.这可以通过部署一个使用 Visual Studio 应用到设备.
如果我从 VS 运行命令 devenv/resetuserdata 我得到错误:
命令devenv"无效.
这是来自 VS 的截图:
我手动删除了 CurrencyExchange.csproj.user 并制作:
- 干净
- 重建
- 部署
- 在发布和调试之间更改配置
- 在 ARM、Any CPU 和 x64 之间切换平台
- 其他手鼓跳舞
这是防火墙的配置:
没有任何帮助.
在我为 Raspberry Pi 3 重新刷新 Windows IoT 后，问题开始了.
在部署之前.
我阅读了论坛，但没有任何帮助...有什么问题?
更新
当我创建应用程序包时:商店 -> 创建应用程序包，有时它会成功，我得到 CurrencyExchange_1.0.X.0_x86_x64_arm_Debug.appxbundle，但有时我会出错:<块引用>
捆绑包中的所有应用程序包清单必须声明相同的值在 XPath 下[local-name()='Package']/[local-name()='Dependencies'].在带有文件的包的清单中声明的此 XPath 下的值命名CurrencyExchange_1.0.20.0_ARM_Debug.appx"和包全名robodem_1.0.20.0_arm__ya2k1rc7yvhh6"在第 11 行，第 4 列不匹配在清单中为具有文件名的包声明的那些CurrencyExchange_1.0.20.0_x86_Debug.appx"和包全名robodem_1.0.20.0_x86__ya2k1rc7yvhh6"在第 11 行，第 4 列
更新
<块引用>设备更新，现在，在 bundleFailure 原因之后:Windows 不能安装包e0c3666e-088b-4aed-8c79-8f7ddb1541fa_1.0.9.0_arm__ya2k1rc7yvhh6因为这个包依赖于一个找不到的框架.提供由微软发布的框架Microsoft.NET.CoreRuntime.1.0"CN=微软公司，O=微软公司，L=雷德蒙德，S=Washington, C=US"，具有中性或 ARM 处理器架构和最低版本 1.0.23819.0，连同这个包一起安装.这当前名称为Microsoft.NET.CoreRuntime.1.0"的框架安装的是:{} 失败文本:包更新失败、依赖项或冲突验证.(0x80073cf3)
远程部署仍然失败.
我在 VS 中删除/克隆 reinit 项目后重新组装了包.
更新
我的电脑IP地址是192.168.1.46，发出:
Set-Item WSMan:localhostClientTrustedHosts -Value 192.168.1.46没有帮助.
更新
如果我尝试从远程 Power Shell 运行调试器，我会得到:
[192.168.1.17]: PS C:DataUsersadministratorDocuments>MSVSMON.EXE术语MSVSMON.EXE"未被识别为 cmdlet、函数、脚本文件或可运行程序的名称.查看名称的拼写，或者如果包含路径，请验证路径是否正确，然后重试.+ CategoryInfo : ObjectNotFound: (MSVSMON.EXE:String) [], CommandNotFoundException+ FullQualifiedErrorId : CommandNotFoundException更新
我试过
更新
如果我通过启动调试器"选项启动调试器，则会出现错误:
<块引用>未能启动 Visual Studio 远程调试器.远程调试器需要复制到设备中.这可以通过部署一个使用 Visual Studio 应用到设备.
我在通过 VS 部署应用程序时仍然出现同样的错误:
<块引用>未出现 Visual Studio 2015 远程调试器 (MSVSMON.EXE)在远程计算机上运行.这可能是因为防火墙正在阻止与远程计算机的通信.
更新
正如Rita Han在进一步对话中建议的那样，我在树莓派的防火墙和PC的防火墙中都启用了8116，我得到了Ok.终端回答，但搜索8116端口时仍然没有重播聆听过程:
- 从 PC 远程登录
- Raspberry Pi 3 上的 Power Shell
net stat - 在 Windows 设备门户中运行进程
更新
正如我之前写的:我在 Raspberry Pi 3 上打开端口，重新启动设备，这里是截图校对，没有任何东西在监听 8116:
更新
手动启动进程也无济于事
更新
正如 Rita 所问，我共享 .csproj 和 .csproj.user 文件.
.csproj:
适用于 UWP 的 Windows IoT 扩展</SDK参考></项目组><PropertyGroup Condition=" '$(VisualStudioVersion)' == '' 或 '$(VisualStudioVersion)' < '14.0' "><VisualStudioVersion>14.0</VisualStudioVersion></PropertyGroup><PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|AnyCPU'"><DebugSymbols>true</DebugSymbols><OutputPath>binDebug</OutputPath><DefineConstants>DEBUG;TRACE;NETFX_CORE;WINDOWS_UWP;CODE_ANALYSIS</DefineConstants><NoWarn>;2008</NoWarn><NoStdLib>真</NoStdLib><DebugType>完整</DebugType><PlatformTarget>AnyCPU</PlatformTarget><UseVSHostingProcess>false</UseVSHostingProcess><ErrorReport>提示</ErrorReport><CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet><Prefer32Bit>真</Prefer32Bit></PropertyGroup><PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|AnyCPU'"><OutputPath>binRelease</OutputPath><DefineConstants>TRACE;NETFX_CORE;WINDOWS_UWP;CODE_ANALYSIS</DefineConstants><Optimize>true</Optimize><NoWarn>;2008</NoWarn><NoStdLib>真</NoStdLib><DebugType>pdbonly</DebugType><PlatformTarget>AnyCPU</PlatformTarget><UseVSHostingProcess>false</UseVSHostingProcess><ErrorReport>提示</ErrorReport><CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet><Prefer32Bit>真</Prefer32Bit></PropertyGroup><导入项目="$(MSBuildExtensionsPath)MicrosoftWindowsXamlv$(VisualStudioVersion)Microsoft.Windows.UI.Xaml.CSharp.targets"/><!-- 要修改您的构建过程，请将您的任务添加到以下目标之一中并取消注释.存在其他类似的扩展点，请参阅 Microsoft.Common.targets.<目标名称="BeforeBuild"></目标><目标名称="AfterBuild"></目标>--></项目>.csproj.user:
另外，我有个好消息.我找到了种类
我看到调试器正在运行:
但是我在netstat的端口中没有看到它:
这是来自 VS 的新错误:
<块引用>1>------ 部署开始:项目:CurrencyExchange，配置:调试ARM ------
1>DEP0110 : 无法检查远程机器'192.168.1.17' 用于开发者模式.请验证远程工具在远程机器上正确安装，并且正确的远程身份验证模式在项目调试设置中指定.
========== 部署:0 成功，1 失败，0 跳过 ==========
更新
我在 netstat 中使用 [192.168.1.17] 找到了 msvsmon 进程:PS C:DataUsersadministratorDocuments>netstat -b -a:
我在 VS 的 Debug 配置中调整了端口:
但是，我有同样的错误.
如果我尝试从以下位置部署 CurrencyExchange_1.0.9.0_ARM_Debug.appxWindows 设备门户我收到错误:失败原因:Windows 不能安装包 xxx 因为这个包依赖于一个框架找不到.提供框架"Microsoft.NET.CoreRuntime.1.0"...
确保安装依赖项和 .appxbundle.这些依赖文件，例如(ARM设备)，在这个路径:
AppPackagesApp21_1.0.0.0_Debug_TestDependenciesARM
您可以通过设备门户安装这些denpendecies(.appx)->选择应用程序包(.appxbundle)后允许我选择可选包
详细步骤可以参考这个回答.
更新:
<块引用>无法使用 Universal 连接到设备192.168.1.17"验证.请验证正确的远程认证方式在项目调试设置中指定.
在将 UWP 应用程序部署到 Windows IoT Core(版本 17763)时，我可以使用 Visual Studio 2015 Update 3 重现此问题.
有一个类似问题 通过安装与设备上运行的 Windows IoT Core 版本相关的新 Windows SDK 来解决.
<块引用>这似乎是一个错误，反映了 Windows 之间的不匹配安装在 Visual Studio 机器上的 SDK 和操作系统版本物联网设备.
但我无法为 Visual Studio 2015 安装比 14393 更新的 Windows SDK 版本.因此，VS2015 似乎无法在新的 Windows IoT Core 版本(如 17763)上进行远程调试.您需要升级到 VS2017.
I try to deploy WPA application to Windows IoT core 10 from Visual Studio 2015.
When I try to deploy, I get error:
Failed to connect to device '192.168.1.17' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. 0x89740016: Exception from HRESULT: 0x89740016
If I change Auth Mode to none, I get error:
Unable to connect to the Microsoft Visual Studio Remote Debugger named 'minwinpc'. The Visual Studio 2015 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
This is configuration page:
If I try to deploy CurrencyExchange_1.0.9.0_ARM_Debug.appx from Windows Device Portal I get error:
Failure reason: Windows cannot install package e0c3666e-088b-4aed-8c79-8f7ddb1541fa_1.0.9.0_arm__ya2k1rc7yvhh6 because this package depends on a framework that could not be found. Provide the framework "Microsoft.NET.CoreRuntime.1.0" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or ARM processor architecture and minimum version 1.0.23819.0, along with this package to install. The frameworks with name "Microsoft.NET.CoreRuntime.1.0" currently installed are: {} Failure text: Package failed updates, dependency or conflict validation. (0x80073cf3)
This is screenshot from Device Portal:
If I try to enable debugging in Device Portal, I get error:
Failed to start the Visual Studio Remote Debugger. The Remote Debugger needs to be copied to the device. This can be done by deploying an application to the device using Visual Studio.
If I run command devenv /resetuserdata from VS I get error:
Command "devenv" is not valid.
This is screenshot from VS:
I removed CurrencyExchange.csproj.user manually and made:
- Clean
- Rebuild
- Deploy
- Change configuration between Releas and Debug
- Change platforms between ARM, Any CPU and x64
- Other dancing with a tambourine
This is configuration of firewall:
Nothing helps.
Problems started after I reflashed Windows IoT for Raspberry Pi 3.
Before it was deploying.
I read forums but nothing helps... What can be a problem?
UPDATE
When I create App Package: Store -> Create App Package, some times it succeeds, and I get CurrencyExchange_1.0.X.0_x86_x64_arm_Debug.appxbundle, but some times I get error:
All app package manifests in a bundle must declare the same values under the XPath [local-name()='Package']/[local-name()='Dependencies']. The values under this XPath declared in the manifest for the package with file name "CurrencyExchange_1.0.20.0_ARM_Debug.appx" and package full name "robodem_1.0.20.0_arm__ya2k1rc7yvhh6" at line 11, column 4 don't match those declared in the manifest for the package with file name "CurrencyExchange_1.0.20.0_x86_Debug.appx" and package full name "robodem_1.0.20.0_x86__ya2k1rc7yvhh6" at line 11, column 4
UPDATE
Device is updated, now, after bundleFailure reason: Windows cannot install package e0c3666e-088b-4aed-8c79-8f7ddb1541fa_1.0.9.0_arm__ya2k1rc7yvhh6 because this package depends on a framework that could not be found. Provide the framework "Microsoft.NET.CoreRuntime.1.0" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or ARM processor architecture and minimum version 1.0.23819.0, along with this package to install. The frameworks with name "Microsoft.NET.CoreRuntime.1.0" currently installed are: {} Failure text: Package failed updates, dependency or conflict validation. (0x80073cf3)
Remote deploy still failing.
I reassembled bundle after remove/clone reinit project in VS.
UPDATE
My PC IP address is 192.168.1.46, issuing:
Set-Item WSMan:localhostClientTrustedHosts -Value 192.168.1.46
Doesn't help.
UPDATE
If I try to run debugger from remote Power Shell, I get:
[192.168.1.17]: PS C:DataUsersadministratorDocuments> MSVSMON.EXE
The term 'MSVSMON.EXE' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
+ CategoryInfo : ObjectNotFound: (MSVSMON.EXE:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
UPDATE
I tried this answer, and this didn't helps.
UPDATE
As Rita Han suggested I uploaded two dependencies, and application successfully deployed. I can run it on the device. How ever, I have nothing runs over 8116 port:
UPDATE
If I start the debugger via Start Debugger option, I get error:
Failed to start the Visual Studio Remote Debugger. The Remote Debugger needs to be copied to the device. This can be done by deploying an application to the device using Visual Studio.
And I still have same error when deploying application via VS:
The Visual Studio 2015 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer.
UPDATE
As Rita Han suggested in further conversation, I enabled 8116 in both firewall of the raspberry and firewall of the PC, I get Ok. terminal answer, but I still have no replay when search 8116 port listening process:
- telnet from PC
- Power Shell
net staton Raspberry Pi 3 - Running Processes in Windows Device Portal
UPDATE
As I wrote before: I opened port on Raspberry Pi 3, restarted device, and here is screenshot proofing, that there is nothing listening for 8116:
UPDATE
To start process manually also don't helps
UPDATE
As Rita asks, I share .csproj and .csproj.user files.
.csproj:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<Import Project="$(MSBuildExtensionsPath)$(MSBuildToolsVersion)Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)$(MSBuildToolsVersion)Microsoft.Common.props')" />
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition=" '$(Platform)' == '' ">x86</Platform>
<ProjectGuid>{AB466423-7430-49A4-AF63-2F6C031394BC}</ProjectGuid>
<OutputType>AppContainerExe</OutputType>
<AppDesignerFolder>Properties</AppDesignerFolder>
<RootNamespace>CurrencyExchange</RootNamespace>
<AssemblyName>CurrencyExchange</AssemblyName>
<DefaultLanguage>en-US</DefaultLanguage>
<TargetPlatformIdentifier>UAP</TargetPlatformIdentifier>
<TargetPlatformVersion>10.0.14393.0</TargetPlatformVersion>
<TargetPlatformMinVersion>10.0.10586.0</TargetPlatformMinVersion>
<MinimumVisualStudioVersion>14</MinimumVisualStudioVersion>
<FileAlignment>512</FileAlignment>
<ProjectTypeGuids>{A5A43C5B-DE2A-4C0C-9213-0A381AF9435A};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
<PackageCertificateKeyFile>CurrencyExchange_TemporaryKey.pfx</PackageCertificateKeyFile>
<AppxAutoIncrementPackageRevision>True</AppxAutoIncrementPackageRevision>
<AppxBundle>Always</AppxBundle>
<AppxBundlePlatforms>x86|x64|arm</AppxBundlePlatforms>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|x86'">
<DebugSymbols>true</DebugSymbols>
<OutputPath>binx86Debug</OutputPath>
<DefineConstants>DEBUG;TRACE;NETFX_CORE;WINDOWS_UWP</DefineConstants>
<NoWarn>;2008</NoWarn>
<DebugType>full</DebugType>
<PlatformTarget>x86</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>true</Prefer32Bit>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|x86'">
<OutputPath>binx86Release</OutputPath>
<DefineConstants>TRACE;NETFX_CORE;WINDOWS_UWP</DefineConstants>
<Optimize>true</Optimize>
<NoWarn>;2008</NoWarn>
<DebugType>pdbonly</DebugType>
<PlatformTarget>x86</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>true</Prefer32Bit>
<UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|ARM'">
<DebugSymbols>true</DebugSymbols>
<OutputPath>binARMDebug</OutputPath>
<DefineConstants>DEBUG;TRACE;NETFX_CORE;WINDOWS_UWP</DefineConstants>
<NoWarn>;2008</NoWarn>
<DebugType>full</DebugType>
<PlatformTarget>ARM</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>true</Prefer32Bit>
<UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|ARM'">
<OutputPath>binARMRelease</OutputPath>
<DefineConstants>TRACE;NETFX_CORE;WINDOWS_UWP</DefineConstants>
<Optimize>true</Optimize>
<NoWarn>;2008</NoWarn>
<DebugType>pdbonly</DebugType>
<PlatformTarget>ARM</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>true</Prefer32Bit>
<UseDotNetNativeToolchain>false</UseDotNetNativeToolchain>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|x64'">
<DebugSymbols>true</DebugSymbols>
<OutputPath>binx64Debug</OutputPath>
<DefineConstants>DEBUG;TRACE;NETFX_CORE;WINDOWS_UWP</DefineConstants>
<NoWarn>;2008</NoWarn>
<DebugType>full</DebugType>
<PlatformTarget>x64</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>true</Prefer32Bit>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|x64'">
<OutputPath>binx64Release</OutputPath>
<DefineConstants>TRACE;NETFX_CORE;WINDOWS_UWP</DefineConstants>
<Optimize>true</Optimize>
<NoWarn>;2008</NoWarn>
<DebugType>pdbonly</DebugType>
<PlatformTarget>x64</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<Prefer32Bit>true</Prefer32Bit>
<UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>
</PropertyGroup>
<ItemGroup>
<!-- A reference to the entire .Net Framework and Windows SDK are automatically included -->
<None Include="project.json" />
</ItemGroup>
<ItemGroup>
<Compile Include="App.xaml.cs">
<DependentUpon>App.xaml</DependentUpon>
</Compile>
<Compile Include="CalibratorBox.cs" />
<Compile Include="CalibratorTestStorage.cs" />
<Compile Include="CommonDelegates.cs" />
<Compile Include="ConstantsConsts.cs" />
<Compile Include="ConstantsMessages.cs" />
<Compile Include="ConstantsExceptions.cs" />
<Compile Include="EnumsSeverity.cs" />
<Compile Include="EnumsStatus.cs" />
<Compile Include="ControlswHeader.xaml.cs">
<DependentUpon>wHeader.xaml</DependentUpon>
</Compile>
<Compile Include="ExceptionsInvalidNodeType.cs" />
<Compile Include="ExceptionsUnhandledControlStatus.cs" />
<Compile Include="ExceptionsUnhandledMessageSeverity.cs" />
<Compile Include="SettingswIncasation.xaml.cs">
<DependentUpon>wIncasation.xaml</DependentUpon>
</Compile>
<Compile Include="SettingswNominals.xaml.cs">
<DependentUpon>wNominals.xaml</DependentUpon>
</Compile>
<Compile Include="SettingswUpload.xaml.cs">
<DependentUpon>wUpload.xaml</DependentUpon>
</Compile>
<Compile Include="ControlswMoneyAdjust.xaml.cs">
<DependentUpon>wMoneyAdjust.xaml</DependentUpon>
</Compile>
<Compile Include="PageswManual.xaml.cs">
<DependentUpon>wManual.xaml</DependentUpon>
</Compile>
<Compile Include="PageswMainPage.xaml.cs">
<DependentUpon>wMainPage.xaml</DependentUpon>
</Compile>
<Compile Include="PropertiesAssemblyInfo.cs" />
<Compile Include="PageswSettings.xaml.cs">
<DependentUpon>wSettings.xaml</DependentUpon>
</Compile>
<Compile Include="PageswStatistics.xaml.cs">
<DependentUpon>wStatistics.xaml</DependentUpon>
</Compile>
</ItemGroup>
<ItemGroup>
<AppxManifest Include="Package.appxmanifest">
<SubType>Designer</SubType>
</AppxManifest>
<None Include="CurrencyExchange_TemporaryKey.pfx" />
</ItemGroup>
<ItemGroup>
<Content Include="PropertiesDefault.rd.xml" />
<Content Include="AssetsLockScreenLogo.scale-200.png" />
<Content Include="AssetsSplashScreen.scale-200.png" />
<Content Include="AssetsSquare150x150Logo.scale-200.png" />
<Content Include="AssetsSquare44x44Logo.scale-200.png" />
<Content Include="AssetsSquare44x44Logo.targetsize-24_altform-unplated.png" />
<Content Include="AssetsStoreLogo.png" />
<Content Include="AssetsWide310x150Logo.scale-200.png" />
</ItemGroup>
<ItemGroup>
<ApplicationDefinition Include="App.xaml">
<Generator>MSBuild:Compile</Generator>
<SubType>Designer</SubType>
</ApplicationDefinition>
<Page Include="ControlswHeader.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="SettingswIncasation.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="SettingswNominals.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="SettingswUpload.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="ControlswMoneyAdjust.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="PageswManual.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="PageswMainPage.xaml">
<Generator>MSBuild:Compile</Generator>
<SubType>Designer</SubType>
</Page>
<Page Include="PageswSettings.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
<Page Include="PageswStatistics.xaml">
<SubType>Designer</SubType>
<Generator>MSBuild:Compile</Generator>
</Page>
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..........RoboLineIoTIoT.csproj">
<Project>{2f12492d-4625-4edf-8497-d9e49f320bef}</Project>
<Name>IoT</Name>
</ProjectReference>
<ProjectReference Include="..LibCurrencyExchange.LibCurrencyExchange.Lib.csproj">
<Project>{5299129a-cee9-4530-8789-e2dcd7d24430}</Project>
<Name>CurrencyExchange.Lib</Name>
</ProjectReference>
<ProjectReference Include="..LibTouchPanelsTouchPanels.csproj">
<Project>{8220b292-cf54-43af-8873-5ad16715fc8a}</Project>
<Name>TouchPanels</Name>
</ProjectReference>
</ItemGroup>
<ItemGroup>
<SDKReference Include="WindowsIoT, Version=10.0.14393.0">
<Name>Windows IoT Extensions for the UWP</Name>
</SDKReference>
</ItemGroup>
<PropertyGroup Condition=" '$(VisualStudioVersion)' == '' or '$(VisualStudioVersion)' < '14.0' ">
<VisualStudioVersion>14.0</VisualStudioVersion>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|AnyCPU'">
<DebugSymbols>true</DebugSymbols>
<OutputPath>binDebug</OutputPath>
<DefineConstants>DEBUG;TRACE;NETFX_CORE;WINDOWS_UWP;CODE_ANALYSIS</DefineConstants>
<NoWarn>;2008</NoWarn>
<NoStdLib>true</NoStdLib>
<DebugType>full</DebugType>
<PlatformTarget>AnyCPU</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet>
<Prefer32Bit>true</Prefer32Bit>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|AnyCPU'">
<OutputPath>binRelease</OutputPath>
<DefineConstants>TRACE;NETFX_CORE;WINDOWS_UWP;CODE_ANALYSIS</DefineConstants>
<Optimize>true</Optimize>
<NoWarn>;2008</NoWarn>
<NoStdLib>true</NoStdLib>
<DebugType>pdbonly</DebugType>
<PlatformTarget>AnyCPU</PlatformTarget>
<UseVSHostingProcess>false</UseVSHostingProcess>
<ErrorReport>prompt</ErrorReport>
<CodeAnalysisRuleSet>MinimumRecommendedRules.ruleset</CodeAnalysisRuleSet>
<Prefer32Bit>true</Prefer32Bit>
</PropertyGroup>
<Import Project="$(MSBuildExtensionsPath)MicrosoftWindowsXamlv$(VisualStudioVersion)Microsoft.Windows.UI.Xaml.CSharp.targets" />
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
<Target Name="BeforeBuild">
</Target>
<Target Name="AfterBuild">
</Target>
-->
</Project>
.csproj.user:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<AppxPackageIsForStore>False</AppxPackageIsForStore>
<AppxShowAllApps>False</AppxShowAllApps>
<AppxBuildConfigurationSelection>x86|x64|arm</AppxBuildConfigurationSelection>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|ARM'">
<DeviceId>30F105C9-681E-420b-A277-7C086EAD8A4E</DeviceId>
<UseEmulator>false</UseEmulator>
<RemoteDebugMachine>192.168.1.17</RemoteDebugMachine>
<AuthenticationMode>None</AuthenticationMode>
<RemoteDebugEnabled>true</RemoteDebugEnabled>
<DeploymentType>CopyToDevice</DeploymentType>
<RemoveNonLayoutFiles>true</RemoveNonLayoutFiles>
<CreateCleanLayout>true</CreateCleanLayout>
<EnableUnmanagedDebugging>false</EnableUnmanagedDebugging>
<DebugEngines>
</DebugEngines>
<BackgroundTaskDebugEngines>
</BackgroundTaskDebugEngines>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Release|ARM'">
<DeviceId>30F105C9-681E-420b-A277-7C086EAD8A4E</DeviceId>
<UseEmulator>false</UseEmulator>
<RemoteDebugEnabled>true</RemoteDebugEnabled>
<AuthenticationMode>Universal</AuthenticationMode>
<RemoteDebugMachine>192.168.1.17</RemoteDebugMachine>
</PropertyGroup>
</Project>
In addition, I have good news. I found kind manual in this forum. I run debugger on Raspberry, and have new error in visual studio.
I see that debugger running:
However I don't see it among ports in netstat:
And this is new error from VS:
1>------ Deploy started: Project: CurrencyExchange, Configuration: Debug ARM ------
1>DEP0110 : Unable to check remote machine '192.168.1.17' for developer mode. Please verify that the remote tools are installed correctly on the remote machine, and that the correct remote authentication mode is specified in the project debug settings.
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
UPDATE
I found msvsmon process in netstat using [192.168.1.17]: PS C:DataUsersadministratorDocuments> netstat -b -a:
And I adjusted the port in Debug config in VS:
However, I had same error.
If I try to deploy CurrencyExchange_1.0.9.0_ARM_Debug.appx from Windows Device Portal I get error: Failure reason: Windows cannot install package xxx because this package depends on a framework that could not be found. Provide the framework "Microsoft.NET.CoreRuntime.1.0"...
Make sure you install the dependencies along with the .appxbundle. These dependencies files, for example(ARM device), in this path:
AppPackagesApp21_1.0.0.0_Debug_TestDependenciesARM
You can install these denpendecies(.appx) via device portal->Allow me to select optional packages after Select the application package(.appxbundle)
Detailed steps you can refer to this answer.
Update:
Failed to connect to device '192.168.1.17' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings.
I can reproduce this issue with Visual Studio 2015 Update 3 when deploying a UWP application to Windows IoT Core (version 17763).
There is a similar issue that solved by install new Windows SDK related to the version of Windows IoT Core running on the device.
This seems to be an error reflecting a mismatch between the Windows SDK installed on the Visual Studio machine and the OS version on the IoT device.
But I can't install newer version than 14393 of Windows SDK for Visual Studio 2015. So it seems VS2015 can't remote debug on new Windows IoT Core version like 17763. You need upgrade to VS2017.
这篇关于无法使用通用身份验证连接到设备“192.168.1.17"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
