Thanks for your comments about Mono support. I can confirm that support for running Reflector under Mono will be officially dropped with the release of version 7. We'd planned to make an announcement about this shortly but, since you've asked, I'm happy to provide some more detail about why this is. Incidentally, although I didn't make direct mention of it in my EA announcement I did allude to this when I described how v7 needs .NET 3.5 or later to run:
http://www.simple-talk.com/community/bl ... 96204.aspx
Obviously this news will come as a disappointment to some, but we made the decision for a couple of reasons.
Firstly, we want to keep Reflector current in terms of support for newer technologies. This may still have been possible whilst continuing to limit ourselves to .NET 1.x compatibility, but would have become increasingly difficult and would ultimately limit our ability to develop the tool in the way we'd like. Whilst Mono supports many of the technologies in later framework versions, a crucial missing link is WPF, which would have a big impact on what we could do with the UI, and also what we might be able to do to provide specific support for technologies such as Silverlight. Certainly there are things we can do without this but, as I've said, it will become increasingly difficult for us to take the tool forward as we'd like with our hands tied technologically.
This leads me onto the second reason...
It's possible none of the above would matter if Mono were in relatively widespread use throughout the Reflector community, but the final nail in the coffin was the realisation that amongst Reflector users Mono is less commonly installed (never mind used) than .NET 1.x, and we'd already taken the decision to stop supporting the latter. Due to this very low penetration amongst Reflector users I could justify neither the extra effort required to support Mono, nor the restrictions supporting it would place on future development.
Note that I'm not making any comment on the overall adoption of Mono, just its prevalence in the Reflector userbase.
Obviously any assemblies compiled with Mono (or .NET 1.x, for that matter) should continue to open fine in Reflector.
If Mono implemented WPF we might take another look at it, although there are some stability issues running on Mono, which I mentioned in an earlier post, that I think we'd need to take a look at before I'd be happy to claim official support.
I hope that clarifies matters for you and, once again, thanks for posting your feedback.