Fix conflicting test assembly name in classloader tests #93012
Merged
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
dd52 was building test.dll and dev10_897464 was building Test.dll which caused assembly resolving conflicts: > warning MSB3243: No way to resolve conflict between "Test, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" and "test, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null". Choosing "Test, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" arbitrarily. Fixed by making the test assembly names unique for each test.
ghost
assigned 
akoeplinger
added
area-Infrastructure-coreclr
and removed
area-TypeSystem-coreclr
labels
|
Tagging subscribers to this area: @hoyosjs Issue Detailsdd52 was building test.dll and dev10_897464 was building Test.dll which caused assembly resolving conflicts:
Fixed by making the test assembly names unique for each test.
|
trylek
approved these changes
Oct 4, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
dd52 was building test.dll and dev10_897464 was building Test.dll which caused assembly resolving conflicts:
Fixed by making the test assembly names unique for each test.