-
Notifications
You must be signed in to change notification settings - Fork 285
Fix deployment regression #6718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
50890ab
to
2076026
Compare
2076026
to
d12d208
Compare
/backport to rel/4.0 |
Started backporting to rel/4.0: https://github.com/microsoft/testfx/actions/runs/18463577664 |
/backport to rel/4.0 |
Started backporting to rel/4.0: https://github.com/microsoft/testfx/actions/runs/18463790290 |
/backport to rel/4.0 |
Started backporting to rel/4.0: https://github.com/microsoft/testfx/actions/runs/18464005693 |
/backport to rel/4.0 |
Started backporting to rel/4.0: https://github.com/microsoft/testfx/actions/runs/18465014328 |
/backport to rel/4.0 |
Started backporting to rel/4.0: https://github.com/microsoft/testfx/actions/runs/18492376996 |
….0) (#6734) Co-authored-by: Youssef1313 <[email protected]>
Fixes #6713
When we introduced the caching of UnitTestElement on the TestCase object, we missed the case where the source gets updated.
When deployment items feature is used, the source points to the assembly in deployment directory, and not from bin. The test assembly should only be loaded ever from the deployment directory. Loading the test assembly twice in the same app domain but in two different contexts (LoadFrom and default contexts) will lead to errors at run time.