From one DLL hell into another, but better, nicer, shinier hell

.NET was touted as the final solution to the DLL hell. Hell, no!

Trying to install a CLR assembly into SQL Server.

It needs a missing assembly System.Data.Entity. I do not use EF but to hell with it, here you are, I add that DLL to the references. Huh? It does not show up in the output folder. To hell with it! I find it on the target server, in the GAC, and add it to the publish folder. Solved? Hell, no!

Now it needs System.Runtime.Serialization.dll.

Next, it needs SMDiagnostics.dll whatever the fuck that is.

Next, it needs system.componentmodel.dataannotations.

FUCK! Am I supposed to copy 1/2 of the whole .NET into my publish folder? Wasn't .NET supposed to be available to all .NET assemblies, wherever they were?

WTF is wrong with you, Microsoft? Can you find your ass with your both hands, once in a lifetime?

No surprise we have this exodus to crappy shits like Python: MS discredited itself, courtesy Satya Nadella and his hordes of Chicom coders.

Posted by: LinuxLies at 09:08 AM | No Comments | Add Comment
Post contains 191 words, total size 1 kb.