For reference: Test-run results screenshots of before and after this PR changes:

Before (e8e56da)

After

I'm worried about the overhead it adds for rewriting non-WPF assemblies. Every method is visited.

Could we perhaps not add the XAML step if we don't have a reference to PresentationCore? This way if we're not a WPF app we don't pay the price.

I will look into it.

Thanks! Let me know when it's ready, I'll merge.

I think for the issue at hand this should be it!

Besides that I played around with the sources. Would there be interest for PRs regarding a general solution maintenance like central package management, tune .editorconfig (eg. use 2 spaces in csproj files), newer C# features, integration projects building if ILPack sources change (not the case now!) etc. And maybe some performance related stuff like Regex tuning, ordinal string comparison where possible etc.?

Thanks!

I'd like to keep the changes to the project to the absolute necessary minimum. I took over the maintenance to unify various forks, and changes will make maintenance difficult for other forks out there. Also I just don't have the time.

Thank you for your explaination. I understand your sentiment and also your problem with limited time.
As I have done some investigations already, I will propose a few smaller PRs which should be easier to assess. Some of them touch on improving collaboration (like reliable scenario test-runs).
I hope my initiative sits well with you and that you understand that this is in no way meant to negate your concerns.

You can certainly send PRs, and I appreciate the help. Just be mindful of maintainer burden. Things like reformatting every file would not be worth it.