-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Missed dependency? #116
Comments
Interesting - what exact error were you seeing (at run time or build time?) and what was the target of the consuming application? It's entirely possible I need to adjust the dependencies for some set of consumers based on their target, especially if they're .NET Framework apps. |
Happened to my as well while running console application targeting net472. The code:
The exception info:
|
I added System.Reflection.TypeExtensions as a direct dependency to the next version (it was already coming in via transitive dependencies). Hopefully that resolves the issue - I'll close it out but please let me know if the direct package reference is still needed after upgrading to 2.3.1. |
|
Hi @TriEdgeAI - what version of Buildalyzer is this (the latest?), what version of .NET Core (or Framework) is the app running on, and what’s the target of the project being compiled? That’ll help me get to the bottom of why you might be seeing this. Thanks! |
Is this useful? |
I'm getting this
When I tried referencing 4.1.0 manually as a NuGet package. |
Very useful, thanks. I have an idea what the problem might be - I’ll check it out tomorrow and see if I can replicate/fix. Stay tuned. |
I'm pretty sure this was fixed a while ago so I'm going to assume this issue is either resolved or no longer relevant. Please comment or open a new issue if that's incorrect and you're still having trouble. |
Greetings! It looks like you may have missed a dependency. I had to install package "System.Reflection.TypeExtensions" to get it to work. Installing this resolved exception and it all works like a charm.
The text was updated successfully, but these errors were encountered: