3 minutes to read read

Journey of Dependency Injection

Asp.Net Core is one of the gems (I would say) created by Microsoft that has simplified a lot of things and provides a whole lot of things by default out of the box. It based on dot net core which provides inherent capability to run cross platform but to ease out developer life several optimizations were done to enhance productivity.

One such feature is Dependency Injection. Although lately, but Microsoft did included dependency injection as a part of the core product. I have been working Asp.Net MVC since 2010 (or 2011) and started DI with Ninject which was (or is) a wonderful project. During the time I crossed paths with Unity and Autofac during different projects, but more or less the approach remain same. Create a container system, create ‘sort of’ controller factories and then register dependencies. But during all this time one thing that remain constant was additional overhead of creating this shit. So it was a moment of joy (atleast for me) when i say this in recent versions of MVC. And most importantly it is quite stable and performs well out of the box.

Continue reading

1 minute to read

Recently my machine got formatted. While re-installing the system, I didn’t installed Visual Studio 2019 first. I tried SQL Server management studio later and then SQL Server. The reason for this particular order was due that the fact more or less the work was targetted more on central SQL Severs and for personal purposes I basically use an instance of Azure and then later delete it.

During the installation of SQL server, i faced a wierd problem which wasted about an hour of mine as the setup runs and then it shows as components not installed. The only error thrown during the installation was “vs shell installation has failed with exit code 1638” which seems a bit weird. Some quick googling thereafter revealed that Microsoft C++ 2017 Redistributible was the problem.

Continue reading