Re: Back to VB6 and .NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

On Tue, 5 Feb 2008 06:01:51 -0800 (PST), Robert Conley
<robertsconley@xxxxxxxxx> wrote:
in <d055c244-13fa-4d50-ac8a-413e18dd49db@xxxxxxxxxxxxxxxxxxxxxxxxxxx>

On Feb 4, 7:21 pm, Tom Shelton
<tom_shel...@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Only because they are catching it up to C#.

So what was missing between VB.NET and C#. We know C# has the ability
to run unsafe code but what other feature VB.NET didn't have that C#
did? The initial version didn't have unsigned integers but that has
been fixed. So whatever capabilities that VB.NET doesn't have via C#?

Basically the issue here is people aren't taking the time to
understand the technical issues of the .NET platform. This is a
problem because too many are complaining about non-existent problems
rather than focusing on the real problems notably BACKWARDS
COMPATIBILITY. It gives people justification to ignore the complainers
when they show they don't know what they are talking about.

Flailing about with adoption rate and market share is also a red
herring. When a vendor breaks compatibility people will investigate
alternatives. Windows got away with it via DOSut .NET isn't.

And there you have it in a nutshell. A no-brainer!

---
Stefan Berglund
.

Relevant Pages

  • Re: Back to VB6 and .NET
    ... to run unsafe code but what other feature VB.NET didn't have that C# ... understand the technical issues of the .NET platform. ... problem because too many are complaining about non-existent problems ... When a vendor breaks compatibility people will investigate ...
    (microsoft.public.vb.general.discussion)
  • Re: How many people have Javascript turned off?
    ... > The .Net platform is perfectly extensible. ... Rather than complaining about ... > System.Web.UI.Page object model, which isn't going to change, why don't ... > just create your own Page or HttpHandler class and use that? ...
    (microsoft.public.dotnet.framework.aspnet)