NLog use Connection String Name in appsettings
I have an NLog database target that looks like this:
<target xsi:type="Database" name="database"
connectionString="Server=.SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
Is it possible to change the connectionString to use connectionStringName from my appsettings instead?
My appsettings is called dssettings.json and it contains the connection details here:
"DatabaseConfiguration": {
"DatabaseName": "ApplicationOne",
"ConnectionName": "DefaultConnection",
"ConnectionString": "Server=.\SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
},
asp.net logging asp.net-core nlog
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
add a comment |
I have an NLog database target that looks like this:
<target xsi:type="Database" name="database"
connectionString="Server=.SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
Is it possible to change the connectionString to use connectionStringName from my appsettings instead?
My appsettings is called dssettings.json and it contains the connection details here:
"DatabaseConfiguration": {
"DatabaseName": "ApplicationOne",
"ConnectionName": "DefaultConnection",
"ConnectionString": "Server=.\SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
},
asp.net logging asp.net-core nlog
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
1
You shouldn't store the connection string in neither one, its not secure and you could accidentally commit it into your source control management system (Git, CSV etc.). Use user secrets, environment variables or azure key value store
– Tseng
Dec 30 '18 at 12:42
I understand but this is for a small project that has been using appsettings for awhile now.
– JianYA
Dec 30 '18 at 14:04
You could consider using the NLog Configuration API.
– R. Richards
Dec 30 '18 at 15:22
add a comment |
I have an NLog database target that looks like this:
<target xsi:type="Database" name="database"
connectionString="Server=.SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
Is it possible to change the connectionString to use connectionStringName from my appsettings instead?
My appsettings is called dssettings.json and it contains the connection details here:
"DatabaseConfiguration": {
"DatabaseName": "ApplicationOne",
"ConnectionName": "DefaultConnection",
"ConnectionString": "Server=.\SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
},
asp.net logging asp.net-core nlog
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
I have an NLog database target that looks like this:
<target xsi:type="Database" name="database"
connectionString="Server=.SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
Is it possible to change the connectionString to use connectionStringName from my appsettings instead?
My appsettings is called dssettings.json and it contains the connection details here:
"DatabaseConfiguration": {
"DatabaseName": "ApplicationOne",
"ConnectionName": "DefaultConnection",
"ConnectionString": "Server=.\SQLEXPRESS;Database=ApplicationOne;Trusted_Connection=True;MultipleActiveResultSets=true;User Id=User0101;Password=PW0101"
},
asp.net logging asp.net-core nlog
asp.net logging asp.net-core nlog
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
asked Dec 30 '18 at 11:55
JianYAJianYA
6541125
6541125
1
You shouldn't store the connection string in neither one, its not secure and you could accidentally commit it into your source control management system (Git, CSV etc.). Use user secrets, environment variables or azure key value store
– Tseng
Dec 30 '18 at 12:42
I understand but this is for a small project that has been using appsettings for awhile now.
– JianYA
Dec 30 '18 at 14:04
You could consider using the NLog Configuration API.
– R. Richards
Dec 30 '18 at 15:22
add a comment |
1
You shouldn't store the connection string in neither one, its not secure and you could accidentally commit it into your source control management system (Git, CSV etc.). Use user secrets, environment variables or azure key value store
– Tseng
Dec 30 '18 at 12:42
I understand but this is for a small project that has been using appsettings for awhile now.
– JianYA
Dec 30 '18 at 14:04
You could consider using the NLog Configuration API.
– R. Richards
Dec 30 '18 at 15:22
1
1
You shouldn't store the connection string in neither one, its not secure and you could accidentally commit it into your source control management system (Git, CSV etc.). Use user secrets, environment variables or azure key value store
– Tseng
Dec 30 '18 at 12:42
You shouldn't store the connection string in neither one, its not secure and you could accidentally commit it into your source control management system (Git, CSV etc.). Use user secrets, environment variables or azure key value store
– Tseng
Dec 30 '18 at 12:42
I understand but this is for a small project that has been using appsettings for awhile now.
– JianYA
Dec 30 '18 at 14:04
I understand but this is for a small project that has been using appsettings for awhile now.
– JianYA
Dec 30 '18 at 14:04
You could consider using the NLog Configuration API.
– R. Richards
Dec 30 '18 at 15:22
You could consider using the NLog Configuration API.
– R. Richards
Dec 30 '18 at 15:22
add a comment |
1 Answer
1
active
oldest
votes
With help from nuget-package NLog.Appsettings.Standard then you can normally do this:
<extensions>
<add assembly="NLog.Appsettings.Standard" />
</extensions>
<targets>
<target xsi:type="Database" name="database"
connectionString="${appsettings:name=DatabaseConfiguration.ConnectionString}"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
</targets>
But because you are using a special dssettings.json (instead of appsettings.json), then you probably have to implement your own custom NLog layout renderer:
https://github.com/NLog/NLog/wiki/How-to-write-a-custom-layout-renderer
Maybe you can use the source-code from the above nuget-package as inspiration for loading dssettings.json. Or maybe create PullRequest that adds support for specifying non-default config-filename.
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
TheConfigurationBuilder.AddJsonFilecan load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.
– Rolf Kristensen
Dec 31 '18 at 8:44
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53977365%2fnlog-use-connection-string-name-in-appsettings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
With help from nuget-package NLog.Appsettings.Standard then you can normally do this:
<extensions>
<add assembly="NLog.Appsettings.Standard" />
</extensions>
<targets>
<target xsi:type="Database" name="database"
connectionString="${appsettings:name=DatabaseConfiguration.ConnectionString}"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
</targets>
But because you are using a special dssettings.json (instead of appsettings.json), then you probably have to implement your own custom NLog layout renderer:
https://github.com/NLog/NLog/wiki/How-to-write-a-custom-layout-renderer
Maybe you can use the source-code from the above nuget-package as inspiration for loading dssettings.json. Or maybe create PullRequest that adds support for specifying non-default config-filename.
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
TheConfigurationBuilder.AddJsonFilecan load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.
– Rolf Kristensen
Dec 31 '18 at 8:44
add a comment |
With help from nuget-package NLog.Appsettings.Standard then you can normally do this:
<extensions>
<add assembly="NLog.Appsettings.Standard" />
</extensions>
<targets>
<target xsi:type="Database" name="database"
connectionString="${appsettings:name=DatabaseConfiguration.ConnectionString}"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
</targets>
But because you are using a special dssettings.json (instead of appsettings.json), then you probably have to implement your own custom NLog layout renderer:
https://github.com/NLog/NLog/wiki/How-to-write-a-custom-layout-renderer
Maybe you can use the source-code from the above nuget-package as inspiration for loading dssettings.json. Or maybe create PullRequest that adds support for specifying non-default config-filename.
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
TheConfigurationBuilder.AddJsonFilecan load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.
– Rolf Kristensen
Dec 31 '18 at 8:44
add a comment |
With help from nuget-package NLog.Appsettings.Standard then you can normally do this:
<extensions>
<add assembly="NLog.Appsettings.Standard" />
</extensions>
<targets>
<target xsi:type="Database" name="database"
connectionString="${appsettings:name=DatabaseConfiguration.ConnectionString}"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
</targets>
But because you are using a special dssettings.json (instead of appsettings.json), then you probably have to implement your own custom NLog layout renderer:
https://github.com/NLog/NLog/wiki/How-to-write-a-custom-layout-renderer
Maybe you can use the source-code from the above nuget-package as inspiration for loading dssettings.json. Or maybe create PullRequest that adds support for specifying non-default config-filename.
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
With help from nuget-package NLog.Appsettings.Standard then you can normally do this:
<extensions>
<add assembly="NLog.Appsettings.Standard" />
</extensions>
<targets>
<target xsi:type="Database" name="database"
connectionString="${appsettings:name=DatabaseConfiguration.ConnectionString}"
commandText="INSERT INTO [SchemaOne].[EventLogs](Id, Message, Level, Logger )VALUES(NewID(), @Message, @Level, @Logger)">
<parameter name="@Message" layout="${message}" />
<parameter name="@Level" layout="${level}" />
<parameter name="@Logger" layout="${logger}" />
</target>
</targets>
But because you are using a special dssettings.json (instead of appsettings.json), then you probably have to implement your own custom NLog layout renderer:
https://github.com/NLog/NLog/wiki/How-to-write-a-custom-layout-renderer
Maybe you can use the source-code from the above nuget-package as inspiration for loading dssettings.json. Or maybe create PullRequest that adds support for specifying non-default config-filename.
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
edited Dec 30 '18 at 16:16
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
answered Dec 30 '18 at 16:09
Rolf KristensenRolf Kristensen
5,4102435
5,4102435
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
TheConfigurationBuilder.AddJsonFilecan load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.
– Rolf Kristensen
Dec 31 '18 at 8:44
add a comment |
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
TheConfigurationBuilder.AddJsonFilecan load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.
– Rolf Kristensen
Dec 31 '18 at 8:44
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
Hello, thank you for replying. Is it possible to have 2 appsettings.json then? So one dssettings.json and one appsettings.json
– JianYA
Dec 30 '18 at 23:23
The
ConfigurationBuilder.AddJsonFile can load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.– Rolf Kristensen
Dec 31 '18 at 8:44
The
ConfigurationBuilder.AddJsonFile can load from any filename. But like I said you have to implement the logic yourself. Maybe offer it as pull-request that allows one to provide custom filename.– Rolf Kristensen
Dec 31 '18 at 8:44
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53977365%2fnlog-use-connection-string-name-in-appsettings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You shouldn't store the connection string in neither one, its not secure and you could accidentally commit it into your source control management system (Git, CSV etc.). Use user secrets, environment variables or azure key value store
– Tseng
Dec 30 '18 at 12:42
I understand but this is for a small project that has been using appsettings for awhile now.
– JianYA
Dec 30 '18 at 14:04
You could consider using the NLog Configuration API.
– R. Richards
Dec 30 '18 at 15:22