Learn More
Resend Email
3
lorentz
1d

IIS, aka Apache But Worse, with the world's shittiest plugin manager, a graphical XML config editor that only shows the attributes of one node at a time, invalid configuration errors that don't tell you anything about which part of the configuration is invalid, and a custom GC config optimized for hosted .NET apps that's somehow even less suitable for hosting than the default desktop GC config.

I had to enable 3 categories of Windows features and 20 additional features that weren't included in the default set for those categories just to host a WCF service.

rant

pain

microsoft

dotnet

wcf

iis
Favorite
Ranter
Comments
  • 0
    1d
    Every day that you haven't yet migrated to asp.net core, Steve Ballmer strangles a newborn otter.

    And if you're using IIS for core then that's some hardcore masochism.
  • 1
    1d
    @donkulator The API is in Core, but the business logic is a 4.x library exposed as a WCF service. I don't often get a say the design, but I did manage to press this issue until everyone had to state that they aren't aware of any applicable benefits of WCF, so it's set to be converted to a plain DLL whenever we get around to it.
  • 0
    1d
    to be clear, I expect to retire before we actually ditch WCF now that consensus has been reached that it's pointless and literally just not having an interface in that position is preferable.
  • 0
    24h
    @donkulator IT will likely stick to IIS after the last of our tech moves away from 4.x and WCF, but by then I won't have to care because besides cohabitant WCF clients and services which often share a runtime, there isn't really a scenario where the presence of IIS affects the behaviour of the application.
  • 0
    11h
    @donkulator you don't even _need_ IIS for classic asp.net - your mileage my vary, but there is a module for apache that allows you to run .net with mono.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment