v4.8 Installers

• Adding Visualizers support for VS 2026

v4.7 Visualizers

• Adding visualizer close button, re: #138
• Writing translated Expressions (etc) to temp files instead of sending them across the debugee/debugger boundary

v4.1.3

• Fixing binary operand type-is checks, re: #143

v4.1.2

Fixing nullable enum translation, re: #134

• Improving ShowCapturedValues capabilities to include captured Linq calls, re: #133
• Fixing parameterless Value Tuple translation, re: #135
• Fixing non-equality enum comparisons, re: #136

v4.1.1

• Fixing static method access when showing captured values re: #129
• Translating enum comparisons as enum constants

v4.6

• Fixing install path miss with non-numeric install directory, re: #127
• Visualizer stability improvements, re: #121
• Adding string.Concat() menu item to visualizer, r: #123
• Adding separate VS17.6+ visualizer, re: #125

v4.1

• Fixing Guid constant translation, re: #119
• Fixing various string concatenation issues, re: #120, 123
• Rendering string.Concat(Object) calls as method calls, not concatenation, re: #116
• Fixing custom method conversion unary translation, re: #117
• Including cast parentheses in cast index access subject, re: #122
• Removing some redundant parentheses in chained binary operations
• Adding setting to translate all string.Concat() calls as method calls, not concatenation

v3.3

• Support for translating unused parameters to discards (_)
• Including ref and out parameter keywords in lambda parameter declarations, re: #106
• Handling null custom Expression values, re: #105
• Translating strings containing any new line characters as verbatim, re: #107
• Support for translating VB.NET named, indexed properties
• Improving variable scope analysis

v3.2

• Support for translating ValueTuples
• Fixing MemberAccess translation regression, re: #101, #103
• Fixing reused ParameterExpression object handling across different scopes

v3.1

• Adding Source Link support
• Fixing part-closed generic array naming, re: #94
• Ensuring generated parameter names are valid, re: #97
• Removing redundant member names in anonymous type member assignments