Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error: Could not load file or assembly 'PresentationFramework' on tlbexport #204

Closed
mgaffigan opened this issue Nov 14, 2023 · 2 comments · Fixed by #205
Closed

Error: Could not load file or assembly 'PresentationFramework' on tlbexport #204

mgaffigan opened this issue Nov 14, 2023 · 2 comments · Fixed by #205

Comments

@mgaffigan
Copy link
Contributor

When using dscom to export a library referencing WPF or another unavailable library, exceptions are thrown from ComAliasNameResolver. We don't really want to "fix" those reference problems, just to have tlbexport ignore them. LibraryWriter already has the logic to turn missing references into warnings, but ComAliasNameWriter is missing them.

Related to #120, PR incoming
@mgaffigan mgaffigan mentioned this issue Nov 14, 2023
Merged
@SOsterbrink
Copy link
Member

@mgaffigan : I started a new Release v1.4.0 so that you can use your fix. It should take a few minutes until it's available.

@mgaffigan
Copy link
Contributor Author

Thanks for the quick merge, and for making dscom open. It’s a great benefit to the community.

@mgaffigan mgaffigan mentioned this issue Jun 27, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Match ReflectionTypeLoadException handling from LibraryWriter into ComAliasNameResolver
2 participants
@mgaffigan @SOsterbrink