After setting up Windows 10 IoT Core on Raspberry Pi 2 and getting all comfortable with it, along comes Visual Studio 2015 with the message: "Please upgrade your remote debugger to match Visual Studio." which apparently means repeating the entire installation (flash from scratch) as described here http://ms-iot.github.io/content/en-US/win10/SetupRPI.htm
Is a "reinstall from scratch" the only way to currently update the Windows 10 IoT Core ? What about something like apt-get update?
With the release of Windows 10 IoT Core build 10586, you can update Windows IoT over the Internet just like we do in Windows.
To update Windows IoT, follow the steps:
Connect your Raspberry Pi 2's Ethernet to the Internet (i.e. with Internet Router or Modem).
Connect your computer/tablet to the same network on which Raspberry Pi 2 is connected.
Open Windows IoT's Web-management portal.
Login to the Web-management portal.
From the left black-panel 'UTILITIES', click 'Windows Update'.
Finally, to update Windows 10 IoT Core, click on 'Check for updates' button and wait for the magic.
Newer to web management portal?
Please refer "Web-Management Portal" section of this ProTip article: https://www.hackster.io/AnuragVasanwala/windows-10-iot-core-setting-startup-app-887ed0
Related
My Setup:
Windows 10 VM running in VirtualBox on Windows 7 Pro
Raspberry Pi 3 running Windows 10 IoT Core - 10.0.16299.19
The VM can see the RaspberryPi/Wionows IoT
I know this because:
On the VMI I can Install and Debug from Visual Studio 2017 to the Pi.
On the VM the IoT Dashboard detects the PI and allows me to change
settings
On the VM I can access the Pi's Device Portal
On the VM I can use Powershell to log in to the Pi.
What I can't do is use Windows IoT Remote Client. Which I want so I can see changes produced by my code.
When I start the client I get the spinning buffer animation followed by a blank, white screen.
I have tried the following as recommended in web articles:
Reset the Pi resolution to 800x600 - This killed the Pi's ability to
display at all; including on the attached HDMI.
Checked Enable Windows IoT Remote Server in Device Portal. - This is
set to On
Disconnected the HDMI from the Pi - Made no difference.
Typed the following into an Admin level PowerShell:
net start WinRM
Set-Item WSMan:\localhost\Client\TrustedHosts -Value
PiName
This allowed Powershell access but no change to Remote Desktop
What should I try next?
On version 16299,the Windows IoT Remote client does not work for Raspberry Pi. Please reference the know issue of release notes for Windows 10 IoT 16299.Currently you can attach a monitor for local display.
Try starting the NanoRDP server manually (not through the web interface) and see if that helps. That has solved a few issues for me.
I believe the executable is in c:\windows\ and is called nanordpserver.exe. just SSH or Powershell into the device, run nanordpserver.exe and try again.
The lightweight RDP protocol that IoT Core uses is not as robust as the version installed on the full Windows 10 OS.
Can I create a webapplication on my windows 10 IOT running device (R-PI 3)?
On other PI's I've got Debian running with LightHttpd, but I can't seem to find anything on a webserver on Win10 IOT device.
I did see some examples on self creating a -very simple- webserver (ie listening on a port) but there should be more than that?
PS
I added 2 tages: Windows IOT and Windows-10-IOT-Core.... are these the same?
Can I create a webapplication on my windows 10 IOT running device
(R-PI 3)?
Yes, you can start with Hello blinky official sample. There are also Python and Node.js supported.
Using ASP.NET, you can publish Web Application on Windows IoT core. (Note the version of ASP.NET, more detailed information is here.)
And, restup is a HTTP server for universal windows platform (UWP) apps that can run on Raspberry Pi with Windows IoT core.
PS I added 2 tages: Windows IOT and Windows-10-IOT-Core.... are these
the same?
Windows IoT core is an edition of Windows 10 differs from desktop and mobile editions. It is optimized for smaller devices with limited resources, such as Raspberry Pi 2 and 3.
Window IoT is something about Internet of Things you can create with Windows.
For tags in SO, "Windows IoT core" and "Window IoT" have identical function.
There are a couple of ways to do this that I've come across which might interest you:
1) As you suggest, it is very simple as you suggest to write you're own server app or app service that listens on a port and responds. Here is a decent example which was easy to follow and implement:
https://sandervandevelde.wordpress.com/2016/04/08/building-a-windows-10-iot-core-background-webserver/
2) Also, it is possible to develop a plugin for Windows Device Portal (WDP) by following the instructions here:
https://learn.microsoft.com/en-us/archive/msdn-magazine/2017/october/windows-device-portal-write-a-windows-device-portal-packaged-plug-in
I have tried this and it works very nicely. It demonstrates how to serve static content and dynamic content either from the foreground or a background task.
I have Windows Server R2 DataCenter w/Hyper-V running, installed the SDK's for Windows Phone development and the Windows Phone Emulator 8.1 U1 is running. On my Windows 8.1 I use Visual Studio 2013 Community for my Universal App development and its also installed on the server.
As of now I have not made any settings changes on the server, so everything is at its default. I already had a working Universal App project running before deciding to use my server (due to I broke my Windows Phone device the other day) for testing my Window Phone app.
Now I have to do all my Windows Phone development on the Server after making modifications and addition to my Windows App on my development machine (NOTE: Windows 8.1 doesn't have a VT cpu).
So my question is, is it possible to add the Windows Emulator 8.1 U1 to my Windows 8.1 project from the Server? This way I don't to keep going to the Server to test the Windows Phone app.
Updated 4-1-2015: additional information and better explanation of question.
Thanks!...
As I understand, you'd like to be able to do the following:
You have a machine X for development, which you can't install emulators on
You have a server Y w/ Phone emulator running
You want to deploy your app directly from machine X to server Y
Unfortunately, remote debugging/deployment to an emulator hosted on a different machine is not supported by VS, at least as far as I'm aware. :(
One thing you could try is using Team Foundation Build to automatically build and deploy your app on your R2 server. You could implement it such that anytime you checked code in, it would be available for ad-hoc testing on your server a few minutes later. This would still mean using Remote Desktop to use the remote emulator, but it would automate the work of getting your changes over to the server. That way you wouldn't have to develop directly on the server.
I am trying to install SQL Server 2008 Enterprise Edition on Windows Server 2008. I have done all the process till the Installation correctly. However, the installer displays the message "Managed SQL Server Installer has stopped working".
No online Solution has been provided yet....
Anyone sorted this problem before?
This is usually a problem with your installation of .NET framework. E.g:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/34671131-a095-4068-b4d8-ab5ef6f5b8cc/managed-sql-server-installer-has-stopped-working
Check that your installations are all in working order by using the tools on this site:
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
You may have to re-install any or all of your .NET framework versions.
Instead of trying several methods that have not been approved, it is better to repair the MSSQL Server installation. On the other hand, there is some other issues that can be encountered during the repair process i.e. Installing the .NET Framework 3.5 on Windows 8, Windows 8.1 and Windows 10 as shown below.
In this case, if you have trouble during .NET Framework installation, you can install it by following the steps below (requires Windows 8, 8.1 or 10) setup disc or ISO file):
1) First you'll need to copy Windows 8 setup files to your hard disk. If you have Windows 8 setup ISO copied in your system, you can mount it by right-click on it and select "Mount" option or you can extract its content using 7-Zip.
If you have Windows 8 setup disc and don't want to copy its content, its ok. Just insert the disc in your CD/DVD drive so that Windows can access its content.
2) Now open Command Prompt as Administrator as mentioned here and then provide following command:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:F:\sources\sxs /LimitAccess
Here "F:" represents the CD/DVD drive letter in your system which contains Windows 8 setup disc. Replace it with the correct drive letter according to your system.
If you extracted Windows 8 setup files in a directory, replace F:\sources\sxs with the correct path.
3) As soon as you execute the above mentioned command, Windows will start installing .NET Framework 3.5 in your system and it'll not require Internet connection.
It'll take a few minutes and you'll get a message that the operation completed successfully.
4) That's it. Now you have installed .NET Framework 3.5 in Windows 8 without using Internet connection.
For more information have a look at How to Install Microsoft .NET Framework 3.5 Offline in Windows 8 and Later without Internet Connection?. Hope this helps...
Visual Studio lets you fire up a Windows 8 simulator to test apps. By default, the simulator uses the same user account as my machine. Is there a way to specify a different account?
This answer comes with one important caveat: It will require an installable (registerable) version of Windows 8.
Use the Hyper-V Manager to create a new virtual machine and install Windows 8 on that. You will be able to create whatever accounts you need, either local or Microsoft accounts. Install the Visual Studio 2012 Remote Debugging tool on that machine. In my case, I joined the VM to my local WORKGROUP.
In your VS 2012 project, you can then select Remote Machine instead of Simulator or Local. If, for some reason, the remote connections dialog box doesn't show up to allow you to select the VM, you can also go to Properties > Debug > Start Options and select Remote Machine and use the Find button to locate it.