Strategy Pattern with ASP.Net Core DI
While building my Rest API I stumbled across building a Cached Repository based on this Article.
Building a CachedRepository via Strategy Pattern
I liked the idea because the code seemed nice and dry. Therefore I went and gave it a shot and the Implementation was quite nice.
However now I want to wire up my DI (the Standard Microsoft DI coming with ASP.Net Core and nothing fancy) and I am Facing some trouble there.
Basically the problem is that I have multiple implementation of the same interface and the cached implementation takes a reference to the direct implementation like so:
public class CachedArticleRepository : IArticleRepository
{
public CachedArticleRepository(IArticleRepository article, IMemoryCache cache)
{
_article = article;
_cache = cache;
}
}
public class ArticleRepository : IArticleRepository
{
public ArticleRepository(IAmbientContextLocator locator)
{
_locator = locator;
}
}
I use it in my service (as explained by the Article) like this:
public class DivisionService : IDivisionService
{
public DivisionService(IArticleRepository article)
{
_article = article;
}
}
My Question is now how can I configure the DI so that the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else?
c# asp.net-core dependency-injection asp.net-core-webapi
edited Nov 26 '18 at 8:47
Steven
128k17221337
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
add a comment |
While building my Rest API I stumbled across building a Cached Repository based on this Article.
Building a CachedRepository via Strategy Pattern
I liked the idea because the code seemed nice and dry. Therefore I went and gave it a shot and the Implementation was quite nice.
However now I want to wire up my DI (the Standard Microsoft DI coming with ASP.Net Core and nothing fancy) and I am Facing some trouble there.
Basically the problem is that I have multiple implementation of the same interface and the cached implementation takes a reference to the direct implementation like so:
public class CachedArticleRepository : IArticleRepository
{
public CachedArticleRepository(IArticleRepository article, IMemoryCache cache)
{
_article = article;
_cache = cache;
}
}
public class ArticleRepository : IArticleRepository
{
public ArticleRepository(IAmbientContextLocator locator)
{
_locator = locator;
}
}
I use it in my service (as explained by the Article) like this:
public class DivisionService : IDivisionService
{
public DivisionService(IArticleRepository article)
{
_article = article;
}
}
My Question is now how can I configure the DI so that the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else?
c# asp.net-core dependency-injection asp.net-core-webapi
edited Nov 26 '18 at 8:47
Steven
128k17221337
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
use the factory delegate when registering the service
– Nkosi
Nov 26 '18 at 0:09
1
TheCachedArticleRepositoryclass is an implementation of the Decorator design pattern.
– Steven
Nov 26 '18 at 8:50
add a comment |
While building my Rest API I stumbled across building a Cached Repository based on this Article.
Building a CachedRepository via Strategy Pattern
I liked the idea because the code seemed nice and dry. Therefore I went and gave it a shot and the Implementation was quite nice.
However now I want to wire up my DI (the Standard Microsoft DI coming with ASP.Net Core and nothing fancy) and I am Facing some trouble there.
Basically the problem is that I have multiple implementation of the same interface and the cached implementation takes a reference to the direct implementation like so:
public class CachedArticleRepository : IArticleRepository
{
public CachedArticleRepository(IArticleRepository article, IMemoryCache cache)
{
_article = article;
_cache = cache;
}
}
public class ArticleRepository : IArticleRepository
{
public ArticleRepository(IAmbientContextLocator locator)
{
_locator = locator;
}
}
I use it in my service (as explained by the Article) like this:
public class DivisionService : IDivisionService
{
public DivisionService(IArticleRepository article)
{
_article = article;
}
}
My Question is now how can I configure the DI so that the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else?
c# asp.net-core dependency-injection asp.net-core-webapi
edited Nov 26 '18 at 8:47
Steven
128k17221337
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
While building my Rest API I stumbled across building a Cached Repository based on this Article.
Building a CachedRepository via Strategy Pattern
I liked the idea because the code seemed nice and dry. Therefore I went and gave it a shot and the Implementation was quite nice.
However now I want to wire up my DI (the Standard Microsoft DI coming with ASP.Net Core and nothing fancy) and I am Facing some trouble there.
Basically the problem is that I have multiple implementation of the same interface and the cached implementation takes a reference to the direct implementation like so:
public class CachedArticleRepository : IArticleRepository
{
public CachedArticleRepository(IArticleRepository article, IMemoryCache cache)
{
_article = article;
_cache = cache;
}
}
public class ArticleRepository : IArticleRepository
{
public ArticleRepository(IAmbientContextLocator locator)
{
_locator = locator;
}
}
I use it in my service (as explained by the Article) like this:
public class DivisionService : IDivisionService
{
public DivisionService(IArticleRepository article)
{
_article = article;
}
}
My Question is now how can I configure the DI so that the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else?
c# asp.net-core dependency-injection asp.net-core-webapi
c# asp.net-core dependency-injection asp.net-core-webapi
edited Nov 26 '18 at 8:47
Steven
128k17221337
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
edited Nov 26 '18 at 8:47
Steven
128k17221337
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
edited Nov 26 '18 at 8:47
Steven
128k17221337
edited Nov 26 '18 at 8:47
Steven
128k17221337
edited Nov 26 '18 at 8:47
Steven
128k17221337
128k17221337
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
asked Nov 25 '18 at 23:54
BrezelmannBrezelmann
448
448
use the factory delegate when registering the service
– Nkosi
Nov 26 '18 at 0:09
1
TheCachedArticleRepositoryclass is an implementation of the Decorator design pattern.
– Steven
Nov 26 '18 at 8:50
add a comment |
use the factory delegate when registering the service
– Nkosi
Nov 26 '18 at 0:09
1
TheCachedArticleRepositoryclass is an implementation of the Decorator design pattern.
– Steven
Nov 26 '18 at 8:50
use the factory delegate when registering the service
– Nkosi
Nov 26 '18 at 0:09
use the factory delegate when registering the service
– Nkosi
Nov 26 '18 at 0:09
1
1
The
CachedArticleRepository class is an implementation of the Decorator design pattern.– Steven
Nov 26 '18 at 8:50
The
CachedArticleRepository class is an implementation of the Decorator design pattern.– Steven
Nov 26 '18 at 8:50
add a comment |
1 Answer
1
active
oldest
votes
Use the factory delegate overload when registering the service
//...
services.AddScoped<ArticleRepository>();
services.AddScoped<IArticleRepository, CachedArticleRepository>(serviceProvider => {
IArticleRepository nonCachedVarient = serviceProvider.GetService<ArticleRepository>();
IMemoryCache cache = serviceProvider.GetService<IMemoryCache>();
return new CachedArticleRepository (nonCachedVarient, cache);
});
//...
That way the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else.
The above code assumes all other dependencies are added to the service collection.
The CachedArticleRepository is registered as IArticleRepository so it will be resolved whenever that dependency is needed.
You can change the service life time to suit your needs. AddScoped was used just to demonstrate the registration process.
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
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%2f53473199%2fstrategy-pattern-with-asp-net-core-di%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
Use the factory delegate overload when registering the service
//...
services.AddScoped<ArticleRepository>();
services.AddScoped<IArticleRepository, CachedArticleRepository>(serviceProvider => {
IArticleRepository nonCachedVarient = serviceProvider.GetService<ArticleRepository>();
IMemoryCache cache = serviceProvider.GetService<IMemoryCache>();
return new CachedArticleRepository (nonCachedVarient, cache);
});
//...
That way the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else.
The above code assumes all other dependencies are added to the service collection.
The CachedArticleRepository is registered as IArticleRepository so it will be resolved whenever that dependency is needed.
You can change the service life time to suit your needs. AddScoped was used just to demonstrate the registration process.
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
add a comment |
Use the factory delegate overload when registering the service
//...
services.AddScoped<ArticleRepository>();
services.AddScoped<IArticleRepository, CachedArticleRepository>(serviceProvider => {
IArticleRepository nonCachedVarient = serviceProvider.GetService<ArticleRepository>();
IMemoryCache cache = serviceProvider.GetService<IMemoryCache>();
return new CachedArticleRepository (nonCachedVarient, cache);
});
//...
That way the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else.
The above code assumes all other dependencies are added to the service collection.
The CachedArticleRepository is registered as IArticleRepository so it will be resolved whenever that dependency is needed.
You can change the service life time to suit your needs. AddScoped was used just to demonstrate the registration process.
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
add a comment |
Use the factory delegate overload when registering the service
//...
services.AddScoped<ArticleRepository>();
services.AddScoped<IArticleRepository, CachedArticleRepository>(serviceProvider => {
IArticleRepository nonCachedVarient = serviceProvider.GetService<ArticleRepository>();
IMemoryCache cache = serviceProvider.GetService<IMemoryCache>();
return new CachedArticleRepository (nonCachedVarient, cache);
});
//...
That way the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else.
The above code assumes all other dependencies are added to the service collection.
The CachedArticleRepository is registered as IArticleRepository so it will be resolved whenever that dependency is needed.
You can change the service life time to suit your needs. AddScoped was used just to demonstrate the registration process.
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
Use the factory delegate overload when registering the service
//...
services.AddScoped<ArticleRepository>();
services.AddScoped<IArticleRepository, CachedArticleRepository>(serviceProvider => {
IArticleRepository nonCachedVarient = serviceProvider.GetService<ArticleRepository>();
IMemoryCache cache = serviceProvider.GetService<IMemoryCache>();
return new CachedArticleRepository (nonCachedVarient, cache);
});
//...
That way the Non Cached Variant is used for building the Cached Repository and the Cached Repository is used for everything else.
The above code assumes all other dependencies are added to the service collection.
The CachedArticleRepository is registered as IArticleRepository so it will be resolved whenever that dependency is needed.
You can change the service life time to suit your needs. AddScoped was used just to demonstrate the registration process.
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
answered Nov 26 '18 at 0:33
NkosiNkosi
119k17137201
119k17137201
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
add a comment |
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
Worked like a Charm thank you for making and saving my day (again) @Nkosi :D
– Brezelmann
Nov 29 '18 at 13:04
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%2f53473199%2fstrategy-pattern-with-asp-net-core-di%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
use the factory delegate when registering the service
– Nkosi
Nov 26 '18 at 0:09
1
The
CachedArticleRepositoryclass is an implementation of the Decorator design pattern.– Steven
Nov 26 '18 at 8:50