Re: From VB.net to C#
"Thomas Eyde" <email@example.com> wrote:
>Consistent or not, in VB6 this way of doing it was a good thing. In .Net
>number of keywords are too many, so a new way should be invented.
>VB.Net is not consistent with Property Get/Let. And then there is the arcane
>syntax of attributes, which is not consistent with anything.
>The new Class statement declares its inheritance in a separate line, so
>what's wrong with methods doing the same thing?
Sounds like you just don't like the language, and that is okay. If you want
something a little less wordy, try C#. There are an awful lot of features,
but you don't have to use most of them for day to day stuff, and they are
there if and when you need them.
If you don't like that, try J#. Java is a very simple language, and mostly
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL