Map real application hierarchies
Fallback & Configuration
Keep modular and inherited view models resolvable without giving up compile-time safety.
Explore source ↗Capability
Exact types, generic definitions, base classes, and interfaces participate in a deterministic fallback order controlled by compiler-visible MSBuild properties.
- 01
Exact, generic, base, and interface lookup
- 02
Referenced-assembly opt-in
- 03
Custom namespace and type transforms
- 04
Additional view base types and accessibility rules
How it composes
From intent
to working system.
Configure
MSBuild exports conventions and assembly scope to the generator.
Index
Factories are grouped by exact and generalized type identity.
Fallback
Runtime lookup follows exact, generic, base, then reverse-interface order.
Explain
Unresolved candidates remain available for useful missing-view output.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package StaticViewLocator<PackageReference Include="StaticViewLocator" Version="VERSION" /><PackageVersion Include="StaticViewLocator" Version="VERSION" /><PropertyGroup> <StaticViewLocatorViewModelNamespacePrefixes>MyApp.ViewModels;MyApp.Modules</StaticViewLocatorViewModelNamespacePrefixes> <StaticViewLocatorIncludeReferencedAssemblies>true</StaticViewLocatorIncludeReferencedAssemblies> <StaticViewLocatorTypeNameReplacementRules>ViewModel=View;Vm=Page</StaticViewLocatorTypeNameReplacementRules></PropertyGroup>Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.