Replies: 1 comment 9 replies
-
We don't set up the execution environment or the dependency resolution at all when running in .NET Core. That's done by VSTest. One way to verify this would be to port a single test to NUnit or MSTest and see if you get the same kind of result via |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm just starting the process of migrating an API to .NET Core. The Api needs to create a fire & forget job via Hangfire. The issue is that the job/delegate that is used to enqueue the Hangfire job needed to reference a .NET Framework assembly because that is not getting migrated yet.
I added the reference to my .NET Framework assembly and called via this line:
I've ran the API locally and submitted to it via Postman and the API successfully schedules that Hangfire job (and it executes) without issue.
However, when I try to run my integration tests against the api (and currently I'm not even testing this method, I just have a skeleton test project enabled for someone else to step in and start building tests), I get the following exception on all 3 of my endpoints that are tested.
I think this is something going on with xUnit (or my misuse) vs FastEndpoints since the Api works on its own??
Beta Was this translation helpful? Give feedback.
All reactions