I know that DI(dependency injection) is probably just another good pattern out there like many others, but dear lord have I been burned on it with acumatica. Acumatica just loves having friggen magic crap everywhere with no damn explanation(*may be in a blog post somewhere but that’s no replacement for good documentation).

I believe they use AutoFac in C# on an asp.net server. They love to utilize reflection and injection and in turn the server takes multiple minutes to startup whilst it dynamically registers everything, as well on any individual pages.

Development is a pain in the ass on this damn system.

I’m constantly having to dive into the damn code using dotpeek to understand what the fuck they are doing and it’s often friggen stupid shit. They like to reinvent the wheel a fair bit.

My visceral hate of Spring.Net burns with the force of a thousand suns.

Almost everything it does is done wrong or solved better by other solutions.

Specifying which classes to instantiate from .xml files? Sure why not, compile type safety (the whole reason for using a static programming language) is obviously overrated and dependency based injection is surely impossible!
And for extra bonus points, now our client code must be aware of the internals of the service classes, and all of their references as well, because, encapsulation? Who cares.

Have you made an typo? Good fucking luck finding out from which of the 100 config files we have floating around...

And, because it has baked in AOP and Transactions its woven into the fabric of the project like a tapewom.

Of course this may just be how our "special snowflake" project uses Spring.

What makes it more painful is that I love good DI tools (ninject, castlewindsor, autofac, there are so many...) and we're stuck with this turd because 7 years ago some java devs couldn't be arsed to learn a new library...

My project setup:
-Entity Framework (Code first)
-Autofac (Dependency Injection)
-Asp.Net MVC C# with service layer pattern.

How is your setup? :)

Unit testing with NSubstitute and Autofac
For the most part, I find it a lot simpler than SimpleInject (hmm) and Moq, which I have used previously.

But there are still some of those 'Oh, for fucks sake!'-gotchas.

I was trying to test a class today where I wanted to substitute all other methods in the class than the one I wanted to test == an actual unit test.

I had previously found out how to do this:

1. Make sure the methods that should be substituted are internal to allow substitution.

2. Substitute class with Substitute.ForPartsOf<T>(args)

3. Set up methods that should not be called with instance.When(a => a.Method()).DoNotCallBase()

This way, you can unit test a class properly and only call the method that you want to test, and also control the return values of the other methods if needed.

So as I said, I have used this before to great effect. But today I just could NOT get it to work! I checked and rechecked everything but the test code kept calling the implementations of the substituted methods!

I even called over another dev for help, but he couldn't see the problem either.

Aargh!

I scoured the internet, but everyone just told me what I already knew: follow the 3 steps, and all is well. Not so!

I ALMOST considered doing the test improperly, as in, increasing the scope beyond that of the method I wanted to test.

But then it hit me... My project was missing this line in AssemblyInfo.cs:

[assembly: InternalsVisibleTo("DynamicProxyGenAssembly2")]

I always add a line to make internals visible to the test project, but I had forgotten that NSubstitute needs this line as well to work properly.

Sometimes when a test fails it will tell you that you are missing this line. And sometimes it just doesn't work.

Maybe I will remember this in the future now. Maybe 😅

Hangfire, Autofac and Web API ! Only if i can figure out this shit😖😖