Requirement engineering, coding, photography
After having done the view parts (Blazor Wasm – custom authentication – Part 1) now it’s time for the model.
Starting with reading the JWT into a List of Claims, so that we can pass it later into a own implementation of AuthenticationStateProvider.
After we already managed to communicate with an BLE device, let’s now try something a bit easier.
As mentioned in a previous post, we already have some “requirements” for a treasure hunt. For that, we need a solution to get the users location.
Let’s see if we can manage to get the location directly from a webapplication and get around the need of writing and deploying a full Mobile App.
Continue reading “Blazor Web geolocation – Android”Description on how to do Remote Debugging websites on Android
Starting the new blazor project as described in it’s documentation
dotnet new blazorwasm -o Solution --hosted cd Solution/Server dotnet watch
And we’re greeted by the typical Blazor start
The ports on which your page will be shown are set random on project creation. You can find (and change) them in “launchSettings.json”.
