I want to connect to the servers,
but computer says: "nooooooooo"

There is no such thing as an unnecessary semicolon! God damn it!

Visual Studio's intellisence recommending me NOT to use

ISomeService = new Service() and just Service coz the latter is faster (these are non-DI services)

is giving me a wierd anxiety. I'd prefer to stick to exposing Interfaces just as a convention but the constant💡is killing me :v
//I know the actual performance difference is neglible, but retarded mind still focuses on it even if I dont want it to

Generally speaking Microsoft's documentation has gotten extremely good.

Generally speaking.

I have projects that, at this point, would get considerable benefit from being able to write parts directly in IL. Sometimes this is for performance, sometimes this to be able to express things that are valid IL, but not expressable in C# or VB or F#. If you work a lot with language you probably know what I'm talking about.

Microsoft hasn't just not documented anything for doing serious IL development, they straight up haven't provided anything to make it easy. No IL projects. No IL syntax/intellisence in VS. Nada.

There is ILSupport, a third party extension which does offer this, even mixed language/IL projects which would be perfect for what I need.

Except Microsoft made a change in the newer SDK's which broke the extension. Where ildasm and ilasm use to be, isn't where it now is.

I'm working with the extension author to come up with a new solution but the lack of documentation and easy/reliable access to those tools is irritating.

Really fucking sick of Visual Studio losing all intellisence on CSHTML files.

We've had MVC for how many goddamned years and they still can't properly integrate a fucking view file into Visual Studio so it works consistently?

Oh and I love how when I changed the name of a class, it ignores every stupid CSHTML