ICredentialProvider in combination with DbContext BotFramework v4
I am using a MultiCredentialProvider that implements the Microsoft.Bot.Connector.Authentication.ICredentialProvider interface. It works with static values but as soon as I try to pass a repository which uses a DbContext to retrieve my bot credentials, it fails with the following message.
System.InvalidOperationException: An attempt was made to use the context while it is being configured. A DbContext instance cannot be used inside OnConfiguring since it is still being configured at this point. This can happen if a second operation is started on this context before a previous operation completed. Any instance members are not guaranteed to be thread safe.
This is caused because the repository should be scoped and not just passed to an object to use in a later stage. The repository is resolved in the ConfigureServices method of the Startup class.
var sp = services.BuildServiceProvider();
var repository = sp.GetService<SomeRepository>();
services.AddBot<SomeBot>(options => {
options.CredentialProvider = new MultiCredentialProvider(configuration, repository);
})
The question is, how can I resolve the service on demand to avoid this error? Is it possible to resolve the whole CredentialProvider, so I can make use of constructor injection? Anything else that I am missing here?
--
Update:
As a temporary workaround, I first get the credentials list from the database, then construct the object and pass the credentials to the MultiCredentialProvider constructor. The only problem with this is that everything is assigned at startup and cannot be changed at a later time. Still looking for better solutions.
c# asp.net-core dependency-injection
add a comment |
I am using a MultiCredentialProvider that implements the Microsoft.Bot.Connector.Authentication.ICredentialProvider interface. It works with static values but as soon as I try to pass a repository which uses a DbContext to retrieve my bot credentials, it fails with the following message.
System.InvalidOperationException: An attempt was made to use the context while it is being configured. A DbContext instance cannot be used inside OnConfiguring since it is still being configured at this point. This can happen if a second operation is started on this context before a previous operation completed. Any instance members are not guaranteed to be thread safe.
This is caused because the repository should be scoped and not just passed to an object to use in a later stage. The repository is resolved in the ConfigureServices method of the Startup class.
var sp = services.BuildServiceProvider();
var repository = sp.GetService<SomeRepository>();
services.AddBot<SomeBot>(options => {
options.CredentialProvider = new MultiCredentialProvider(configuration, repository);
})
The question is, how can I resolve the service on demand to avoid this error? Is it possible to resolve the whole CredentialProvider, so I can make use of constructor injection? Anything else that I am missing here?
--
Update:
As a temporary workaround, I first get the credentials list from the database, then construct the object and pass the credentials to the MultiCredentialProvider constructor. The only problem with this is that everything is assigned at startup and cannot be changed at a later time. Still looking for better solutions.
c# asp.net-core dependency-injection
add a comment |
I am using a MultiCredentialProvider that implements the Microsoft.Bot.Connector.Authentication.ICredentialProvider interface. It works with static values but as soon as I try to pass a repository which uses a DbContext to retrieve my bot credentials, it fails with the following message.
System.InvalidOperationException: An attempt was made to use the context while it is being configured. A DbContext instance cannot be used inside OnConfiguring since it is still being configured at this point. This can happen if a second operation is started on this context before a previous operation completed. Any instance members are not guaranteed to be thread safe.
This is caused because the repository should be scoped and not just passed to an object to use in a later stage. The repository is resolved in the ConfigureServices method of the Startup class.
var sp = services.BuildServiceProvider();
var repository = sp.GetService<SomeRepository>();
services.AddBot<SomeBot>(options => {
options.CredentialProvider = new MultiCredentialProvider(configuration, repository);
})
The question is, how can I resolve the service on demand to avoid this error? Is it possible to resolve the whole CredentialProvider, so I can make use of constructor injection? Anything else that I am missing here?
--
Update:
As a temporary workaround, I first get the credentials list from the database, then construct the object and pass the credentials to the MultiCredentialProvider constructor. The only problem with this is that everything is assigned at startup and cannot be changed at a later time. Still looking for better solutions.
c# asp.net-core dependency-injection
I am using a MultiCredentialProvider that implements the Microsoft.Bot.Connector.Authentication.ICredentialProvider interface. It works with static values but as soon as I try to pass a repository which uses a DbContext to retrieve my bot credentials, it fails with the following message.
System.InvalidOperationException: An attempt was made to use the context while it is being configured. A DbContext instance cannot be used inside OnConfiguring since it is still being configured at this point. This can happen if a second operation is started on this context before a previous operation completed. Any instance members are not guaranteed to be thread safe.
This is caused because the repository should be scoped and not just passed to an object to use in a later stage. The repository is resolved in the ConfigureServices method of the Startup class.
var sp = services.BuildServiceProvider();
var repository = sp.GetService<SomeRepository>();
services.AddBot<SomeBot>(options => {
options.CredentialProvider = new MultiCredentialProvider(configuration, repository);
})
The question is, how can I resolve the service on demand to avoid this error? Is it possible to resolve the whole CredentialProvider, so I can make use of constructor injection? Anything else that I am missing here?
--
Update:
As a temporary workaround, I first get the credentials list from the database, then construct the object and pass the credentials to the MultiCredentialProvider constructor. The only problem with this is that everything is assigned at startup and cannot be changed at a later time. Still looking for better solutions.
c# asp.net-core dependency-injection
c# asp.net-core dependency-injection
edited Nov 27 '18 at 15:20
emp
asked Nov 21 '18 at 6:18
empemp
2,9842037
2,9842037
add a comment |
add a comment |
0
active
oldest
votes
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%2f53406262%2ficredentialprovider-in-combination-with-dbcontext-botframework-v4%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53406262%2ficredentialprovider-in-combination-with-dbcontext-botframework-v4%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