Skip to main content
Shiny.Net.HttpServer.Mobile package icon

Shiny.Net.HttpServer.Mobile

Mobile lifecycle for Shiny.Net.HttpServer, built on Shiny.Core โ€” stops the server when the app is backgrounded and starts it again on resume, keeps it alive on Android through a foreground service, rebinds when the device changes network, and reports the manifest or bundle entries that otherwise fail silently. For iOS and Android, with or without MAUI.

Total Downloads
650
650
Published
Sep 5, 2026
Latest stable version

Install

.NET CLI
dotnet add package Shiny.Net.HttpServer.Mobile --version 1.1.1
Package Manager Console
Install-Package Shiny.Net.HttpServer.Mobile -Version 1.1.1
PackageReference
<PackageReference Include="Shiny.Net.HttpServer.Mobile" Version="1.1.1" />

Frameworks

net10.0 net10.0-android36.0 net10.0-ios26.0 net10.0-maccatalyst26.0

Dependencies

[1.1.1, )
Shiny.Core
net10.0
[5.6.0-beta-0074, )
[10.0.10, )
Shiny.Net.HttpServer
net10.0-android36.0
[1.1.1, )
[10.0.10, )
Shiny.Core
net10.0-android36.0
[5.6.0-beta-0074, )
[10.0.10, )
[10.0.10, )
Microsoft.Extensions.Options
net10.0-android36.0
[10.0.10, )
[10.0.10, )
Shiny.Net.HttpServer
net10.0-ios26.0
[1.1.1, )
Shiny.Core
net10.0-ios26.0
[5.6.0-beta-0074, )
[10.0.10, )
[10.0.10, )
[10.0.10, )
Shiny.Net.HttpServer
net10.0-maccatalyst26.0
[1.1.1, )
[10.0.10, )
Shiny.Core
net10.0-maccatalyst26.0
[5.6.0-beta-0074, )
[10.0.10, )
[10.0.10, )
Microsoft.Extensions.Options
net10.0-maccatalyst26.0
[10.0.10, )
Microsoft.Extensions.Primitives
net10.0-maccatalyst26.0
[10.0.10, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.

The published metadata declares 32 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.