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
NCrunch wants to be able to load the test assembly in-process, even for v3 test projects (which are typically out of process). This flag would allow us to load the test assembly in-process, on the assumption that NCrunch is already setting up to do all the necessary dependency resolution.
I think I'm going to end up with a flag you can pass for launch options, per our previous discussion. Nothing's wired up yet, but this would be a base set of options that are available to all the front controller methods in v3 runner utility (Find, FindAndRun, and Run):
What it would do for v3 projects would be to load the .exe in-process and find the entry point, and then call it with all the correct arguments. I'm already constructing the argument list on behalf of the out-of-process invocation anyway. If user's customize the entry point, it'll end up calling them just like launching the executable would.
bradwilson
changed the title
Add FrontControllerLaunchOptions.ForceInProcess to support NCrunch
Add FrontControllerLaunchOptions.ForceInProcess to support NCrunch
Jun 9, 2024
Verified that we have provided NCrunch with everything they need for integration at this point. They can open new issues if they uncover specific problems.
NCrunch wants to be able to load the test assembly in-process, even for v3 test projects (which are typically out of process). This flag would allow us to load the test assembly in-process, on the assumption that NCrunch is already setting up to do all the necessary dependency resolution.
Discussion: #2337 (comment)
Edit: This issue has a dependency on #2951 being finished first.
The text was updated successfully, but these errors were encountered: