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();
            }
            else
            {
                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.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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.51 EF 6.0.2 VS2013 It see