So for years our VB chums have not been able to debug in VB without VS crashing while rolling over a class level object. This is a problem in VB 4.3, VB 4.4 and even in VB TinyCLR OS.
So a simple app like this will cause VS to explode if you roll the cursor over I
Option Explicit On Option Strict On Imports Microsoft.SPOT Imports Microsoft.VisualBasic.CompilerServices Namespace MFConsoleApplication1 Public Module Module1 Private I As Integer = 1 Sub Main() Debug.Print(Resources.GetString(Resources.StringResources.String1)) Stop Debug.Print(I.ToString) End Sub End Module End Namespace
Even thou i dont use VB i know a crazy dude in Southern California who is still in love with VB
I looked over the problem, i pondered, i swore at the PC and still i couldn’t figure it out.
As luck would have it i still have @mcalsyn on 0800 HELPDESK speed dial and my caller ID isnt blocked so i says to Martin…Dude…Hook me up…
A day later we now have a VSIX for VS2017 which allows full debugging in VS2017 - a huge win for the VB fanboys
So heres the evidence… CerbuinoBee running a VB app with NETMF 4.4 in VS2017 with full debugging and no explosions…