Skip to main content

Action filter in Ioc - injectable action filters

ASP MVC ofera posibilitatea declararii unor actiuni comune folosind action filter. Odata ce am implementat un action filter, orice controller sau actiune poate sa fie decorata cu comportamentul pe care noi l-am definit. Se aseamana oarecum cum AOP-ul. Pentru mai multe informatii puteti sa gasiti aici.
Dar daca folosim Ioc, ar fi frumos si uneori necesar sa putem injecta action filtere la runtime. Pentru acest lucru propun urmatorul mecanism:
 public class ActionFilterInIocAttribute : ActionFilterAttribute, IActionFilter
{
private IActionFilter _actionFilter;

public ActionFilterInIocAttribute(Type filterType)
{
_actionFilter = Ioc.GetObject(filterType);
}
public void OnActionExecuted(ActionExecutedContext filterContext)
{
_actionFilter.OnActionExecuted(filterContext);
}

public void OnActionExecuting(ActionExecutingContext filterContext)
{
_actionFilter.OnActionExecuting(filterContext);
}
}

Dupa acest moment putem sa declaram orice action filter, care sa implementeze o interfata propie, de exemplu:
    public interface ICustomActionFIlter{}

public class CustomActionFilter : ActionFilterAttribute, ICustomActionFIlter
{
public override void OnActionExecuted(ActionExecutedContext filterContext)
{
//...
}
}

Iar apoi daca vreti sa decorati o actiune cu acest action filter o sa fie nevoie sa faceti urmatorul lucru:
[ActionFilterInIoc(typeof(ICustomActionFIlter))]
public void ActionName(CarViewModel carViewModel)

Aceasta este solutia pe care eu o propuna. Singura problema este ca nu putem folosii direct numele la interfata ca si atribut. Avantajul principal este ca functioneaza pe orice mecanism de Ioc.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…