https://github.com/djaus2/blazgpio

Test dotnet/iot functionality in Blazor App.
https://github.com/djaus2/blazgpio

Last synced: 4 months ago
JSON representation

Test dotnet/iot functionality in Blazor App.

• Host: GitHub
• URL: https://github.com/djaus2/blazgpio
• Owner: djaus2
• License: cc0-1.0
• Created: 2020-10-03T12:58:49.000Z (over 5 years ago)
• Default Branch: main
• Last Pushed: 2020-10-04T03:11:26.000Z (over 5 years ago)
• Last Synced: 2025-10-19T15:39:27.012Z (8 months ago)
• Language: HTML
• Size: 234 KB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# BlazGPIO

Test [dotnet/iot](https://github.com/dotnet/iot) functionality in a Blazor App.

**Blazor WebAssembly app**  

Demonstrates that a Blazor WASM Client can't call hardware directly.  

Can call it via the service though.  

Focus is upon GPIO functionality and Bindings Devices functionality.

## Pages

- All calls fail gracefully if hardware not available.

- Get CPU Core Temperature

  - Gets the CPU Core temperature of a RPi when running Debian/Linux

  - Nb: Does not work with Windows 10 IoT-Core

  - Uses the **CpuTemperature** Device form **IoT.Devices.Bindings**

  - Call to Device is from .ASP.NET Core _(.Net Core functionality)_

- Get Set GPIO Pins

  - Sets or clears a RPi pin

  - Does/should work with Windows 10 IoT-Core as well

  - Uses **System.Device.GPIO** directly

  - System.Device.GPIO is a .NET Standard library

  - Call is from the Shared Library _(Which is also .NET Standard)_

  - Nb: Call can only be via service. Call direct from WASM Client always fails.