Please see the following github issue #26663 in the Rosyln repo for full details with screenshots.
PS: it would be great if there was a repo on github where we could file "CodeRush For Rosyln " issues since that is where we also file issues related to Rosyln itself.
Hi Eric,
Thank you for letting us know about this issue. I reproduced it passed this ticket to our R&D for further research. We'll notify you in the context of this thread once we have any news.
Our team appreciates your idea about having a GitHub repository, but since we depend on our own issue tracker, moving to GitHub will require huge changes in our workflow (at least). Maybe one day we will decide to fully rely on the GitHub ecosystem, but at the moment we do not have such plans.
Hi Igor, many thanks for the prompt reply and I completely understand about relying on your own issue tracker