Shiny Extensions for .NET FAQs

Question 1

What are IInfrastructureModules used for?

Accepted Answer

They allow you to group related service registrations and middleware configurations into a single class, making your ASP.NET Core Program.cs file cleaner and more modular.

Question 2

What is the benefit of attribute-driven DI in Shiny Extensions?

Accepted Answer

It uses source generators to handle service registration at compile-time based on [Singleton], [Scoped], or [Transient] attributes, eliminating the need for long, manual registration lists in your startup code.

Question 3

Does this skill support Blazor WebAssembly?

Accepted Answer

Yes, Shiny Extensions provides specific support for Blazor via the Stores.Web package, allowing you to use localStorage and sessionStorage through the same unified IKeyValueStore interface.

Question 4

How does object-store binding work?

Accepted Answer

By marking a class with [ObjectStoreBinder] or using AddPersistentService, any property changes in a class implementing INotifyPropertyChanged are automatically persisted to the underlying store.

Question 5

What platforms are supported by the key/value stores?

Accepted Answer

The stores support Android (SharedPreferences/Encrypted), iOS/macOS (NSUserDefaults/Keychain), Windows (LocalSettings), and Web (Local/Session Storage).

Shiny Extensions for .NET

Key Features

Use Cases

Shiny Extensions for .NET

Key Features

Use Cases