fix for when a weaver has an AfterWeaving method. #304
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 was working on updating my add-in for jasonwoods-7/Vandelay#2, and I found that when executing the Stamp.Fody add-in, it is throwing the following exception:
The file copy is failing since the ModuleDefinition field is locking the .tmp file.
To test that this is fixed, I added an AfterWeaving method to FakeModuleWeaver.cs in the FodyIsolated.Tests project. The WeavedAssembly_ShouldContainWeavedInfo test in WeavingInfoTests.cs throws the same exception before applying the two Dispose calls I added to InnerWeaver.cs.