is microsoft.visualbasic namespace "true .net" code?


my dev organisation removing prepared start new project. mart "vb shop" given days vb3, nonetheless prevalent opinion we're ".net shop" given c# combined personally .net, since vb.net retrofit, we've solid pierce disrespectful minute c# only. debate revolves around doubt presumably microsoft.visualbasic namespace legitimate place new growth wholly behind harmony vb6 (and older) code. further, some-more engaging doubt presumably formula "under" microsoft.visualbasic namespace even .net formula unequivocally aged vb runtime uniformly finished .net wrapper, origination fact com interop control (similar winforms wraps non-.net win32 windowing api nonetheless exposes wholly .net apis consumption).



to even some-more confusing, the dev organisation microsoft consulting services consultant explanation us microsoft longer supports visible basic, including vb runtime underlying microsoft.visualbasic namespace.



what i'm looking links -- preferably decent microsoft sources -- support definitively answers doubt proceed other. i've already attempted several hunt permutations google gotten any closer removing bottom question.



edit: apparently i didn't doubt clear. i'm seeking vb.net loyal .net code. i'm perplexing establish whatever "under" microsoft.visualbasic namespace .net formula it's aged vb6 runtime uniformly finished unprotected .net code. someone already conspicuous 9/10 namespace simply wraps formula elsewhere .net; 1/10?



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members