-
Notifications
You must be signed in to change notification settings - Fork 45
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
Runs twice on WPF projects #82
Comments
Interesting. I'm gonna follow this to see what you find out :). Seems like this could be related to XAML compilation? I wonder if you can specify attributes in XAML (not counting the partial class parts, just kinda curious if there's something for it since nothing comes to mind). I suspect it will be fine to run Mr. Advice once after it's all done, but not sure if there's a better post-build target to integrate with |
It may be not soon, because I have other priorities, which are moving to .NET Standard and then adding some "advice-reflection" (gathering dependencies of a method, dependencies being methods and fields). |
Runs twice and sometimes crashes once:
|
Does it crash after the build has been cleaned? It might be that it doesn't copy dependencies until the second build? I think the first pass is probably to build the BAML resources from XAML which I don't think requires dependencies to be copied right away |
It used to crash sometimes, I've been working on it and did not see the bug lately. But this is a blurry fix 🤕 |
WPF is weird 🙁 |
On WPF projects, Mr. Advice is invoked twice. Is it good or not?
Something to do with MarkupCompilePass1/MarkupCompilePass2?
The text was updated successfully, but these errors were encountered: