Skip to content

BamlMapTable's KnownAssemblyInfoRecord should be an instance field #589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 16, 2019

Conversation

ryalanms
Copy link
Member

System.Reflection.Assembly.ReflectionOnlyLoad is not supported on .NET core and has been replaced with MetadataLoadContext. MetadataLoadContext is cleared between markup compile passes, invalidating all System.Relection.Assembly instances loaded by MetadataLoadContext.

Various markup compilation errors were occuring because of failed property lookups due to comparisons against an invalid System.Reflection.Assembly instance (PresentationFramework) in BamlMapTable.KnownAssemblyInfoRecord. PresentationFramework is now loaded each time BamlMapTable is created by XamlTypeMapper, per markup compile pass.

This change includes the recommendation from @weltkante's review to update BamlAssemblyInfoRecord on BamlMapTable to be an instance field.

@ryalanms
Copy link
Member Author

@weltkante: Thank you for reviewing. I'll include you on future build task refactor threads. Thanks.

@weltkante
Copy link

weltkante commented Apr 16, 2019

As requested in the other PR I've created issue #591

@ryalanms ryalanms merged commit b85bdfa into master Apr 16, 2019
@rladuca rladuca deleted the dev/ryalanms/weltkante_review_update2 branch June 4, 2019 23:55
@ghost ghost locked as resolved and limited conversation to collaborators Apr 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants