-
Notifications
You must be signed in to change notification settings - Fork 8
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
Solves in reverse order #140
Comments
Hi Melvin, Thanks for suing The reverse order problem has indeed to do with the other issue you pointed out. Based pure observation, types were returned ordered by Your repository also uncovered another issue: Regarding that duplicate being printed, I need to look deeper into that since it involves |
Stop relying on default ordering returned by `Assembly.GetTypes()` This tackles one of the issues raised in #140.
This aims to tackle an issue uncovered in #140.
@MelvinSnijders Could you please test v2.0.2-alpha.1 version and verify that both the ordering issue and the construction exceptions one are fixed? I'll track the double rendering issue separately in #143. |
Just tested it, works great, thanks! |
Awesome to read! |
Using
Solver.SolveAll();
will result in a reverse order, and somehow a duplicate being printed, as seen below:This is my folder structure:
It looks like this issue is related to #137, but I'm not sure why this happens in my case.
The text was updated successfully, but these errors were encountered: