VB.net & Properties

I noticed a problem with deploying an app that uses a class with properties coded like this:

Public Class RegisterUser

    Public Property UserID As String
End Class

When this gets deployed with debugger attached, you get an error FF000000 Unable to resolve System.Diagnostics.DebuggerBrowsableAttribute.

It’s not a major issue as I found an article here that helped saying use the old way of declaring properties (It took a lot of searching to find the right strings to pull up the answer :wink: ):

	Private _userId As String
    Public Property UserID As String
            Return _userId
        End Get
        Set(value As String)
            _userId = value
        End Set
    End Property

I know most people class VB as an obsolete language but is this classed as a bug?


1 Like

What?.. :hand:

I was more lucky and found it in less than half a minute 8)

I’ve had experience at MS coding events where people aren’t interested in helping when they see you are using VB (Hence I rarely go to them now)

Ok I’ve failed my Google^H^H^H^H^H^H^HBing exam :wink:

I guess that is because they simply don’t know VB. VB is by no means obsolete, just look at the new features that are coming: http://blogs.msdn.com/b/vbteam/archive/2014/12/09/new-language-features-in-visual-basic-14.aspx

It is still in the top 10. Actually it is doing better than a year ago (according to TIOBE):


Huh? VB is still alive? I thought c# was supposed to replace it… VB-MF confirmed

VB.NET still has a better VS integration, and is more readable (in my opinion). It is just a language that fits super well with any MS technology. Then again everything else is C based and basing your skills in C# is probably better. You can switch camps if you know C#.