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
In VS2017 V15.2 (26430.6) and maybe other versions as well, the IDE crashes when trying to use this extension with code containing an expression bodied property like: public string MyString3 => _myString3; or public string MyString4 => "C# 6 \"expression body\" feature";.
This is due to EnvDTE CodeProperty.Getter as CodeElement not having implemented the StartPoint property, though this has been working in VS2017 before (VS2015 is OK).
Exception handling is missing to address such issues up to V1.5 Release 2 (Build 20) but nevertheless these string literals will be missing when addressed, because the extension needs the start and end points.
The text was updated successfully, but these errors were encountered:
Just fixed the crash in V1.5 Release 3 (Build 21) but still, the expression bodied properties will not be parsed as long as the StartPoint and EndPoint throw NotImplementedException.
Just worked around the issue by handling not only null references of getters but also exceptions when accessing the getter's StartPoint.
I just hope that eventually the expression bodied properties will see their CodeElement.StartPoint and EndPoint properties set, as before the getter and setter always have been null.
In VS2017 V15.2 (26430.6) and maybe other versions as well, the IDE crashes when trying to use this extension with code containing an expression bodied property like:
public string MyString3 => _myString3;
orpublic string MyString4 => "C# 6 \"expression body\" feature";
.This is due to EnvDTE
CodeProperty.Getter as CodeElement
not having implemented theStartPoint
property, though this has been working in VS2017 before (VS2015 is OK).Exception handling is missing to address such issues up to V1.5 Release 2 (Build 20) but nevertheless these string literals will be missing when addressed, because the extension needs the start and end points.
The text was updated successfully, but these errors were encountered: