You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is and why it's important to you. Ex. I'm always frustrated when [...]
Any (even unsuccessful) ways in which you've tried to workaround the problem currently
I prefer using ILSpy with the C#3.0 "Use LINQ expression syntax" option turned off, however ilspycmd does not expose this option (as far as i can tell as of 8.2.0.7535)
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like some mechanism to specify the linq expression option from the command line.
Additional context
Add any other context or screenshots about the feature request here.
I have also found for de-obfuscated assemblies, the linq expression syntax conversion can lead to naming collisions that are more explicitly scoped in lambda format (which is probably more a de-obfuscator issue than an ilspy issue.)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is and why it's important to you. Ex. I'm always frustrated when [...]
Any (even unsuccessful) ways in which you've tried to workaround the problem currently
related to #2800
I prefer using ILSpy with the C#3.0 "Use LINQ expression syntax" option turned off, however ilspycmd does not expose this option (as far as i can tell as of 8.2.0.7535)
Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like some mechanism to specify the linq expression option from the command line.
Additional context
Add any other context or screenshots about the feature request here.
I have also found for de-obfuscated assemblies, the linq expression syntax conversion can lead to naming collisions that are more explicitly scoped in lambda format (which is probably more a de-obfuscator issue than an ilspy issue.)
The text was updated successfully, but these errors were encountered: