Skip to main content

AOP using RealProxy (custom implementation) - Part II - Register to a IoC container

In the last post of this series we saw how we can use RealProxy to implement our custom AOP stack in .NET that can measure how long a method lasts. In this post we will see what is the mechanism that can be used to register our instance to a IoC container with or without a duration profiler (with or without a proxy).
The solution is pretty simple and can be used with any kind of IoC stack. Basically, when we register our instance to the container we will detect if we need or not to measure how long the methods takes place from our specific class. Based on this information we can register to the container an instance of DurationProfilingDynamicProxy (our custom RealProxy) or not.
In the next example, using a flag read from configuration file we create a specific instance of our Foo objects.
private static IFoo CreateFooInstance(bool isFooProfillingActive)
            IFoo fooOriginalInstance = new Foo();
            IFoo fooContainerInstance = null;
            if (isFooProfillingActive)
                fooContainerInstance = (IFoo) new DurationProfilingDynamicProxy<IFoo>(fooOriginalInstance).GetTransparentProxy();
                fooContainerInstance = fooOriginalInstance;
            return fooContainerInstance;
Dont' forget to call “GetTransparentProxy” to get an instance of the object when we are using a proxy.
new DurationProfilingDynamicProxy<IFoo>(fooOriginalInstance).GetTransparentProxy()
Using the instance returned by the previous method, we will register our instance to the container.
IFoo fooContainerInstance = CreateFooInstance(isFooProfillingActive);
container.RegisterInstance(typeof(IFoo), fooContainerInstance);
The methods that create the instance of our IFoo object could be written also in the following way:
private static IFoo CreateFooInstance(bool isFooProfillingActive)
    IFoo fooInstance = new Foo();
    if (isFooProfillingActive)
        fooInstance = (IFoo) new DurationProfilingDynamicProxy<IFoo>(fooInstance).GetTransparentProxy();
    return fooInstance;
In this post we saw how we can register to IoC container a real implementation or a proxy that measure how long the method takes place using RealProxy. In the next post on this subject we will implement a proxy that writes in the log when a method was called, the input parameters and the result of the call.


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 …

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…

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.