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: README.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Version 2 is here with some new features:
19
19
* Base Optional Tag - The [optional](#optional) tag that some of the builders in this project employed in V1 has been moved into the base class and is now available
20
20
on all key/value config builders.
21
21
* Section Handlers - This feature allows users to develop extensions that will apply key/value config to sections other than `appSettings` and `connectionStrings`
22
-
if desired. Read more about this feature in the [Section Handlers](#sectionhandlers) segment below.
22
+
if desired. Read more about this feature in the [Section Handlers](#section-handlers) segment below.
23
23
24
24
## Key/Value Config Builders
25
25
@@ -346,7 +346,25 @@ collection. As an example, here is what their explicit declaration would look li
When adding additional handlers, the name of the section must be 'Microsoft.Configuration.ConfigurationBuilders.SectionHandlers' so key/value config builders can find it.
349
+
When adding additional handlers, the name of this section must be 'Microsoft.Configuration.ConfigurationBuilders.SectionHandlers' so key/value config builders can find it.
350
+
Also note that a more qualified type will be required so the runtime can determine which assembly contains the new handler type. When working
351
+
with ASP.Net applications, it is hit and miss regarding whether its able to define new section handlers in `App_Code` or not. Some configuration
352
+
sections (such as `appSettings`) get loaded by ASP.Net before `App_Code` is compiled, so handlers for those sections will need to be
353
+
compiled in a separate assembly in the 'bin' directory. For example:
0 commit comments