Summary
Packages like Microsoft.Maui.DevFlow.Logging is currently implemented as a standalone DevFlow logger with no actual MAUI dependency. In sibling repos like wpf-labs, this package is already being reused by non-MAUI platforms such as WPF, Uno Platform, and MewUI.
Problem
The current package name is misleading because it suggests the logger is MAUI-specific. In reality, it is a generic DevFlow logging component that works across platforms.
Recommendation
Rename the package to:
Microsoft.DevFlow.Logging
This would better reflect its cross-platform nature and avoid confusion for consumers using WPF, Uno, MewUI, or other DevFlow hosts.
If backward compatibility is important, keep Microsoft.Maui.DevFlow.Logging as a compatibility alias or package while introducing the new package name.
Additional recommendation
The agent core package might be shrinked and then renamed following the same cross-platform naming approach, as Microsoft.DevFlow.Agent.Core, because it holds many common types.
The analyzer package should follow the same cross-platform naming approach. If reuse of the MAUI analyzer implementation is desired, it should still be exposed from a generic package name such as Microsoft.DevFlow.Analyzers to avoid implying MAUI-only usage.
References
Summary
Packages like
Microsoft.Maui.DevFlow.Loggingis currently implemented as a standalone DevFlow logger with no actual MAUI dependency. In sibling repos likewpf-labs, this package is already being reused by non-MAUI platforms such as WPF, Uno Platform, and MewUI.Problem
The current package name is misleading because it suggests the logger is MAUI-specific. In reality, it is a generic DevFlow logging component that works across platforms.
Recommendation
Rename the package to:
Microsoft.DevFlow.LoggingThis would better reflect its cross-platform nature and avoid confusion for consumers using WPF, Uno, MewUI, or other DevFlow hosts.
If backward compatibility is important, keep
Microsoft.Maui.DevFlow.Loggingas a compatibility alias or package while introducing the new package name.Additional recommendation
The agent core package might be shrinked and then renamed following the same cross-platform naming approach, as
Microsoft.DevFlow.Agent.Core, because it holds many common types.The analyzer package should follow the same cross-platform naming approach. If reuse of the MAUI analyzer implementation is desired, it should still be exposed from a generic package name such as
Microsoft.DevFlow.Analyzersto avoid implying MAUI-only usage.References