Learn More
Resend Email
7
jkuhl
5y

"Exception has been thrown by the target of an invocation"

This error message pisses me off. I know the SSIS Script component is capable of catching exceptions, you can wrap all your code in a try/catch (please don't) and get an exception. So would it be so hard that if the Script Component throws an exception that it tells me what it is instead of sending me on a goddamn scavenger hunt?

The whole bullshit system of errors is why I hate SSIS. Just tell me what went wrong.

I did what I wasn't supposed to do, wrapped it in a try catch and it gave me a stack trace and an error message and all sorts of actionable shit. But why the hell can't it just do that on its own?

There is literally nothing worse, except maybe Hitler, than a goddamn vague error message.

rant
Favorite
Ranter
Comments
  • 1
    5y
    Especially when it's in goddamn passive voice!
  • 0
    5y
    But but mah sucyriteh hardnaehng!

    Sorry, I know it makes sense, but it's a closed network and a noncritical piece of software, would it be so fucking bad if my users could come back to me with a meaningful error message...
  • 0
    5y
    Object was null.
    Value out of range.

    It's all the same; (default) exception handlers could totally tell you all you really want to know but don't because an extra few cycles to handle an exception is too big.
  • 0
    4y
    The idea of extending SSIS with c# functionality is nice, because the "sky's the limit".

    Too bad the implementation makes you think they advocate a horrible programming style.

    Just wrap the entire script with a try-catch clause and be done with it. It doesn't make for nice code but it 'works'.

    Also, why does SSIS *HAVE* to open a new visual studio every time you open a C# script!?
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment