At least one product was developed in VB.NET. We tried to keep the current conventions when maintaining or extending it. It was mostly a wrapper around stored procs, so just a lot of Response.Writes.
For some reason, to me VBScript feels like I can whip up something really quickly, and VB.NET is "all the power of the CLR, with a bit of sugar to help transition to .NET."
VB.NET does feel a bit weird. Maybe some compromises to transition folks to .NET, and from there to C#.
For some reason, to me VBScript feels like I can whip up something really quickly, and VB.NET is "all the power of the CLR, with a bit of sugar to help transition to .NET."
VB.NET does feel a bit weird. Maybe some compromises to transition folks to .NET, and from there to C#.