Resolves #340 - Succeed removing backing field when backing field does not exist #424
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cking field does not exist
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am in the same team as the person who created this issue : #340. We thought the problem would disappear after migrating to .NET8 but we're still having it with version 7.1.1
The ORM seems to try weaving already weaved dlls. The problem occurs randomly in our solution. The solution everytime is to remove the obj folder, restore dependencies, and rebuild.
I'm wondering if telling the weaver that removing backing field is done successfully (which's made in this PR) when the field does not exist anyway would be a good solution ?