Learn More
Resend Email
7
djsumdog
21d

It's amazing just how bad Visual Studio/.NET is .. and the way this shop does stuff.

I was just copying existing projects and renaming/modifying everything for new tasks, but this time I tried to create a new project from scratch. No matter what I get:

Could not load type 'System.Runtime.CompilerServices.RequiredMemberAttribute' from assembly 'NJsonSchema, Version=11.3.2.0, Culture=neutral

Everything has the right .NET framework. Dependencies look mostly identical to other projects. No one in the work chat has seen it before. I'm about to move this project to a tmp dir, copy and existing project, search and replace all the name, empty it out and copy my source into it. What you want to bet it will "just work."

I hate everything about Windows/.NET .. I'm glad I have a job again, but .NET is just so fucking painful. How has Visual Studio remained this bad for this many decades? I swear VS 2022 is just like VS6 with a fucking dark theme.

rant

c#

.net

windows

frustration
Favorite
Ranter
Comments
  • 5
    21d
    Been working with dependencies in linux and windows for a good number of years now. The GAC certainly makes Windows more complicated, but the ecosystem fragmentation in linux makes it just as complicated over there.

    Frankly, you just pick your poison and hope you don't need to support both!
  • 2
    21d
    @AlgoRythm I'd take Linux 100% anytime over Windows. I know Linux bottom to top. I built a Linux From Scratch back in 2001 and used it for two semesters and have spent most of my life on Gentoo.

    If there's a problem in Linux, I can ALWAYS fix it because I can dig down however far I need to in the code. At my last shop, we had a really slick Nix setup to unify dependencies for all Mac and Linux devs. Even in Java, the built is always sane with Gradle, SBT or hell even Maven (🤢)

    I did a whole talk on Docker/Nix and the history of dependencies: https://battlepenguin.video/w/...

    Windows is just dogshit all over the place with horribly broken tooling, and no amount of .NET Core or containers will ever fix it.

    ...also my problem seems to be a know issue and I was directed to another project with an entirely different more convoluted way of pull stuff from Mongo to avoid the issue 😩
  • 3
    21d
    @djsumdog yup DLL hell in Windows can be rare, but real. I’ve had it just a single time but that was largely the projects fault.
  • 0
    21d
    Windows is great, MSVC the best IDE, Linux is a pile of exploded shit that scattered everywhere, Windows a real maintained ecosystem.
  • 3
    21d
    Assembly version issues suck, but date your project. They are a thing of the past in modern .net.

    I've had to fight with these a lot in our legacy framework apps. Double check your assembly redirect configs, and check the actual dll assembly version against it, it doesn't always match the package version.
  • 3
    20d
    VS6 with a dark theme is actually the dream. But new dotnet has so much tooling and code hiding and your project has such a complex list of requirements. The build folder is absolutely crazy.

    With VS6, we did not have all these configurations in this level, in certain way, times were simpler.

    Some trade offs have been made.
  • 1
    20d
    Should sum it up for you quite well.

    https://devopsreactions.tumblr.com/... .

    /jk

    Even w/ all its faults /* which have gotten worse in the current iteration */ I do like Windows, still.
  • 0
    20d
    I only use MSVC with C, C++, Win API and I think it's amazing, I want to learn C#.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment