Posts: 5
Joined: Sun Apr 17, 2016 5:53 am

Best Way to Implement Web Interface - Replace WPD or co-install?

Sun Feb 18, 2018 11:30 pm

For my project, I am trying to figure out the best way to implement a user-friendly web interface, similar to the Windows Device Portal, but tailored to an end user of my IOT product, not it's creator like WDP.
Since the WDP already runs on a web server, would it best to just replace the Portal itself with my own(perhaps hiding the actual portal behind a technician password wall)? Or does this violate some EULA with Microsoft/ is not possible as most of WDP is baked so far into Windows and you'd need to work there to replace it?
If it is the latter, would it be at all damaging to run a second server instance on port 21 hosting my interface, leaving 8080 to the WDP, or would this be likely to overload the OS?
I'd appreciate any help in this, thank you!

Posts: 3
Joined: Tue Feb 20, 2018 9:51 pm

Re: Best Way to Implement Web Interface - Replace WPD or co-install?

Sun Mar 18, 2018 12:10 pm

You can also customize certain parts of the device portal. See ... tal-plugin
It's possible to disable the WDP ... WindowsIoT
Then you can implement your own web-server in uwp ... viceBlinky, or c++ web-server
The OS will not be overloaded if there are multiple web-servers running on it, as long as your web-applications are programmed correctly.
If you want to run on port 21, be sure to disable the built-in ftp service ... device/ftp

Return to “Windows 10 for IoT”