Comments
3 comments
-
Sorry for the delay PeterSimpson it took a fair bit of investigation. The main problem here is related to forward types (TypeForwardedToAttribute) for which Reflector is not able to generate method bodies. We're discussing this internally and will decide a course of action shortly.
-
Thanks @Russell D it's surprising that no-one had noticed this before. I look forward to hearing how this will be addressed.
Thanks, Peter -
This was fixed .Net Reflector 10.3 (ref RP-4211) please see the release notes for further information.
Add comment
Please sign in to leave a comment.
I've just upgraded to v10 and I still can't decompile the .NET Standard system libraries from MS. For example, if I use F12 on a System.Text.RegularExpressions.Regex call in my .NET Framework library I see the inner workings of the Regex class.
However, if I F12 on a System.Text.RegularExpressions.Regex call in the .NET Standard version of my library I just see the method signature and there there is no implementation of the method underneath it.
Please can you let me know how can I use .NET Reflector to view the internals of .NET Standard assemblies from within VS?
I guess this may be impossible since .NET Standard is intended as an interface specification rather than a realisation. If this is the case, I would have expected lack of support for .NET Standard to be clearer on the Redgate web site, because I did look for mention of this before I purchased the upgrade.
Thanks, Peter