![visual basic commenting visual basic commenting](https://i2.wp.com/dailydotnettips.com/wp-content/uploads/2012/01/image4.png)
I think this balances all the concerns and unblocks the customer.
#Visual basic commenting how to
In this article, you are going to learn more about Visual basic commands and how to use them in your code. But now I'd like to propose an alternative. Visual Basic, like any other programming language, employs commands.
![visual basic commenting visual basic commenting](http://1.bp.blogspot.com/-H5xgGxqo22c/UHTRXAk2dbI/AAAAAAAAAK4/TAbTfSj5gHc/w1200-h630-p-k-no-nu/image001-752715.png)
We just didn't have a good heuristic for formatting here at the time. The same problem exists with Case blocks. Ok, that's a bit contrived but there are situations where people want the comment to be considered part of the Then part and other times when it labels the Else part. You lose Pretty Listings, but when un-indenting a comment, it won't auto indent any more. I found something, go to Settings -> Text Editor -> Basic -> Advanced, then turn Pretty Listings off. I'm wondering if I am the only one using VB.Ĭhris solved on, 06:54 AM (6 hours ago), 0 votes: It's now December, still can't put a comment above an ELSE without it auto indenting, and I'm still using VS2013 even though I bought VS2017 when it was released. When using VS2017 it is distracting concentrating on not screwing up comments.Ĭhris Botha solved on, 09:35 PM (4 days ago), 0 votes: Please give me an idea if it is an issue, and if so, if it will be fixed or not, and roughly when.Ĭhris on, 11:15 PM (80 days ago): 6 months later and still under investigation. I also reported this issue with the RC build, and here it still is, nobody said it is an issue or not, if the issue is being looked at/not being looked at, nothing. For a IF THEN ELSE, I cannot put a comment above the ELSE, and make the comment stay above the ELSE, it will always auto indent.ĭoesn't matter if in the Tab settings is none, block or smart, the comment will always auto indent.Įven when typing close to one of these comments in an existing file (created with VB in VS2013), it screws up my existing listings.