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)

public void OnActionExecuting(ActionExecutingContext 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:
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.


Popular posts from this blog

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 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 …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

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…