I've blogged about an issue that has arisen with respect to the fact that the phone has not RTM yet and is stuck on build 10160 whereas the desktop Win 10 has RTMed and is build 10240; as is the Windows SDK. This problem is now solved,
UPDATES:
(1) The latest version of Windows Remote Arduino fixes this. See next.
(2) The latest build of the phone (10512) will also resolve this issue. Windows 10 Build 10512
Version 1.1 of the library has been released. It contains a lot of improvements, such as supporting strings like “A0” in pinMode, analogRead, and getPinMode. You can now get a general pin profile of the device you are connecting to, such as the number of pins and their supported modes. It is now recommend to use the RemoteDevice events “DeviceReady” and “DeviceConnectionFailed” as opposed to the events in the IStream objects, as now we can provide better error messages in case the pin configuration ‘handshake’ fails.
The updated source is available at https://github.com/ms-iot/remote-wiring
The Windows 10 Technical Preview Phone has not RTMed yet and is stuck on build 10160 whereas the desktop Win 10 has RTMed and is build 10240; as is the Windows SDK. Visual Studio 2015 has RTMed also. Win 10 RTM with VS 2015 RTM can't deploy to the current build of the phone (10160). This has an impact upon Windows Remote Arduino development...Using the emulators is not a solution. See query on answers.microsoft.com
Severity Code Description Project File Line Error Error : DEP3321 : To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.10240.0 or higher.
You currently are running version 10.0.10166.0.
Please update your OS, or change your deployment target to a device with the appropriate version. App3
You can unload the project file and then directly edit the project file without leaving Visual Studio:
<?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>{6E07D692-2124-4733-B062-35538FEDACDC}</ProjectGuid> <OutputType>AppContainerExe</OutputType> <AppDesignerFolder>Properties</AppDesignerFolder> <RootNamespace>App3</RootNamespace> <AssemblyName>App3</AssemblyName> <DefaultLanguage>en-US</DefaultLanguage> <TargetPlatformIdentifier>UAP</TargetPlatformIdentifier> <TargetPlatformVersion>10.0.10240.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.10240.0</TargetPlatformMinVersion> <MinimumVisualStudioVersion>14</MinimumVisualStudioVersion>
See the 3rd and 2nd last lines, the target platform version.
This is what I did first: I changed BOTH 10.0.10240.0 entries to 10.0.10160. i.e.:
<TargetPlatformVersion>10.0.10240.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.10240.0</TargetPlatformMinVersion> to <TargetPlatformVersion>10.0.10160.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.10160.0</TargetPlatformMinVersion>
The project would not reload:
Jesse Frush suggested only changing the min version. i,e.:
(Thanks Jesse and Dan)
<TargetPlatformVersion>10.0.10240.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.10240.0</TargetPlatformMinVersion> to <TargetPlatformVersion>10.0.10240.0</TargetPlatformVersion> <TargetPlatformMinVersion>10.0.10160.0</TargetPlatformMinVersion>
The project loaded, built and deployed OK.
I then did the same with my (updated for RTM) Windows Remote Arduino project and it was able to load, build, deploy and run OK.
My Windows Remote Arduino Project:
Porting an RC project to RTM
Win 10-IoT- Universal app - Porting a VS 2015 RC Universal CS app project to RTM_The Changed Project File