New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganizing: Support for VB #245

Closed
codecadwallader opened this Issue Apr 2, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@codecadwallader
Owner

codecadwallader commented Apr 2, 2016

Migrated from https://trello.com/c/TD0jaAab with 15 votes

Note: Johan Gillis did a quick test of just enabling the option and encountered the following:

Tried to enable this option in the CodeMaid menu for 'Basic' and did a test on 2 files. The small one reorganized fine except that the xml comments did not stay with their code items, and the larger (rather complex one) gave a crash (nullreference exception).

Investigated this a little. In a simple scenario an exception will happen when trying to refresh the cursor positions after a move. This works in C# so it seems that the cursor behavior is different for the VB text editor API.

We've resolved the comment headers as part of #231

codecadwallader added a commit that referenced this issue Apr 17, 2016

@codecadwallader codecadwallader added this to the v10.1 milestone Apr 17, 2016

@codecadwallader codecadwallader self-assigned this Apr 17, 2016

@codecadwallader

This comment has been minimized.

Owner

codecadwallader commented Apr 17, 2016

This appears to be working OK in VS2015. I have enabled support and would really appreciate anybody who is regularly using VB to try it out in the CI channel here: http://vsixgallery.com/extension/4c82e17d-927e-42d2-8460-b473ac7df316/ (v10.0.86 or higher)

@codecadwallader

This comment has been minimized.

Owner

codecadwallader commented Apr 17, 2016

I've done some additional testing and it appears this will only work in VS2015. Both VS2012 and VS2013 through the exceptions referenced above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment