Ignore type load errors #222
Open
Conversation
This file contains hidden or 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
Author
|
I solved it in a completely different way. The problem was that one attribute was located in a nuget assembly - that was not loaded correctly. And one attribute implemented an interface from a nuget assembly - that was not loaded correctly either. The reason is that for class libraries nuget assemblies are not copied to the bin folder (anymore?) Setting the property "included assets" : "all" on the package makes it all work again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 have a weird error that when adding another custom attribute to a type I keep getting "Could not load type from assembly" it happens first in GetCustomAttributes, and also a few other places.
By simply ignoring the exceptions (not normally something I would recommend) it just seems to work. I have done a few tests and things like TsOptional are not honored, so I have found significant impact of these changes, but the alternative is the project not working at all.