You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
20
20
21
21
- Removed obsolete serialization constructor and `[Serializable]` attribute from `DotNetConsoleException` as formatter-based serialization is no longer supported or recommended in modern .NET.
22
22
23
+
## [5.0.1] - 2026-03-25
24
+
25
+
### Added
26
+
27
+
-`ConfigureAppConfiguration` method to `DotNetConsoleBuilder` (re-)enabling custom configuration providers
28
+
-`CustomArgumentParsingAttribute` to allow verbs to accept unknown arguments for manual parsing
29
+
30
+
### Fixed
31
+
32
+
- Fixed configuration provider timing: `DotNetConsole.Configuration` now properly reflects all configuration providers (including those added via `ConfigureAppConfiguration`) when accessed early in the application lifecycle.
33
+
23
34
## [5.0.0] - 2025-01-27
24
35
25
36
### Added
@@ -120,7 +131,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
120
131
121
132
- Removed AWS NLog Logger assembly that was used for logging to Amazon CloudWatch
/// Given a configuration delegate that adds a custom configuration source, when building the console, then should be able to access the custom configuration.
configuration[overrideKey].ShouldBe(finalValue);// Should be overridden by the second delegate
220
+
}
221
+
222
+
/// <summary>
223
+
/// Given a configuration delegate that accesses the HostBuilderContext, when building the console, then should have access to environment information.
/// When calling the console app with parameters but without specifying the default verb, and the default options have no properties, it should still run the default command.
165
+
/// This reproduces a customer scenario where they defined isDefault but parse arguments manually in the command.
0 commit comments