Quote:
Originally posted by Peder
I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET, I hate VB.NET!!!!!!!!!!!!!!!!
This was the third time I really tried to learn vb.net, and the same happens every time. I go back to good old' VB6. Can somebody tell me why we needed vb.net? For me it looks like Microsoft tried to make a more advanced version of VB, but failed brutally, and instead made a less intuitive and much harder to use version. How can I make apps with vb.net when the object "app" doesn't exist and the declaration type string is thrown? No, I hope Microsoft makes a VB 7 version to us other! Have anyone else also heard this rumor?
Just feels quite frustrated right now, and wanted to scream it out. Sorry folks :)
I don't have anything against vb.net, besides that I would burn it, dig it 80 feet down and nuke it.
nice view .......lol:D :D