You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the engine is passed an assembly that it cannot examine, the engine throws an exception. This was the correct behaviour at the time of implementation, however our handling of invalid assemblies has since improved.
We should instead suppress the crash, and create some form of NotRunnableFrameworkDriver for the assembly. That will allow the engine and various runners to produce more user-friendly error messages for these cases.
The text was updated successfully, but these errors were encountered:
Interesting. Our DriverService already does what you suggest in the face of a BadImageFormatException.
But this exception comes in the code that initially examines the assembly in order to select a runner and the DriverService isn't in play until we have a runner that needs to create a driver.
I'm pretty sure this worked in the past but we have added more pre-checks to the code before we actually try to load the assembly and probably that's what broke it.
What I'm not getting is why this doesn't happen for Run as well as Explore.
Ah. That would make sense. I think we should go through all the "pre-discovery" we do with Cecil and try to handle errors in a more friendly way.
In terms of the sequence of things, I think we would want to implement #718 first, if you decide to do it. It's still sitting as an "idea" here although I have a vague memory you said something about going ahead with it somewhere else.
I'll try to work on it over the weekend. Considering that I'm not employed and sheltering in place at home, it's amazing how many things I have going on. 😄
See #794.
Currently, if the engine is passed an assembly that it cannot examine, the engine throws an exception. This was the correct behaviour at the time of implementation, however our handling of invalid assemblies has since improved.
We should instead suppress the crash, and create some form of
NotRunnableFrameworkDriver
for the assembly. That will allow the engine and various runners to produce more user-friendly error messages for these cases.The text was updated successfully, but these errors were encountered: