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
I'm sure many of you have noticed that the VBLang discussions has both become toxic and/or dormant. Here is a place where we, as a community, can discuss what we'd like to see with regards to VB. It can also be used to share information of note regarding VB - any news regarding positive things taking place as they relate to VB would be greatly appreciated.
In addition to suggestions and news, we should also strive to find volunteers interested in tackling/addressing the suggestions. Some of this might require interacting with the Roslyn, WinForms, .NET, etc. teams... and that's to be expected. However, let's strive to find ways to address the circumstances first and foremost throughout our own community member contributions, code, documentation, sharing, etc. By doing this, it is my hope that the team member(s) on the Microsoft side of the fence can see that we are ready and willing to address these concerns ourselves, to a high bar... eventually opening the door regarding accepting those pull requests with confidence. This will not happen overnight... we have a long road ahead of us.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
CommunityVB
-
I'm sure many of you have noticed that the VBLang discussions has both become toxic and/or dormant. Here is a place where we, as a community, can discuss what we'd like to see with regards to VB. It can also be used to share information of note regarding VB - any news regarding positive things taking place as they relate to VB would be greatly appreciated.
In addition to suggestions and news, we should also strive to find volunteers interested in tackling/addressing the suggestions. Some of this might require interacting with the Roslyn, WinForms, .NET, etc. teams... and that's to be expected. However, let's strive to find ways to address the circumstances first and foremost throughout our own community member contributions, code, documentation, sharing, etc. By doing this, it is my hope that the team member(s) on the Microsoft side of the fence can see that we are ready and willing to address these concerns ourselves, to a high bar... eventually opening the door regarding accepting those pull requests with confidence. This will not happen overnight... we have a long road ahead of us.
Please join us in this endeavor!
Beta Was this translation helpful? Give feedback.
All reactions