Replies: 1 comment 1 reply
-
#20328 ? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Please note that this is not yet a full bug report (hence not an issue), more like we have hunches that point in a strange direction. Any help in narrowing it down would be appreciated.
We're seeing signs of concurrently running apps getting their views mixed up, i.e. App A using App B's views with Razor Runtime Compilation. Precompiled views without Razor Runtime Compilation don't have this issue.
Details
Our CI environment runs multiple versions of the same app (from multiple branches) in parallel for UI testing.
dotnet build
is used to build the app,dotnet publish
to publish it to a folder. Then,dotnet test
executes UI tests (xUnit tests) which all will start the same app's web app project withdotnet My.App.dll
(which is then interacted with from an automated browser).We see occasions that two concurrently running instances of the app (which are built from slightly different codebases, from different branches of the same repository) get mixed up views if Razor Runtime Compilation is enabled. I.e. App A loads App B's views (so views built from the templates with modifications from App B's branch). Note that the two running apps mostly only differ in a few lines, so e.g. all the DLLs are named the same.
If we turn off Razor Runtime Compilation the issue goes away.
Is this something that can actually happen within Razor Runtime Compilation? We've resolved the issue by turning it off (it was a mistake having it on anyway since the views are actually precompiled) but we figured this is worth bringing it up if there is a chance we encountered a bug.
Further technical details
dotnet --info
:Beta Was this translation helpful? Give feedback.
All reactions