VB.net
-
Man, this is moronic. They provide .exe package for a for a word/pdf/html document... :doh:
I have observed that even MSDN Example code is given as WinZip Self-Extracting executable.
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
I program 100% in VB.Net at the moment (let the flaming begin) and I have no problem with it
"Let's face it, the average computer user has the brain of a Spider Monkey." Bill Gates
Well the "100%" might be the reason you have no problem with it :) Actually, it is more basically preferences and if a person enjoys the VB syntax then fine, if they don't well, there is no reason to use it. Use what you like if it is your choice and don't care what others think..
Rocky <>< Latest Code Blog Post: Linq - One-to-One issues? Latest Tech Blog Post: You got to see this - Seadragon and Photosynth!
-
So I'm currently looking for new work, and the possibility of an interesting opportunity has come up with a local company. The only problem is they use VB.net. I think they had a legacy codebase in VB originally. I've only coded VB when I absolutely have to, although I can look at VB.net code and roughly work out it's intent. I can't imagine it would be too hard to transfer from c# to vb.net, but are there any major differences between the languages? For example, I'm sure I've read pieces recently about various new MS technologies like Linq and WPF and .net 3.5 language features that are only available in c# at the moment. Did I imagine it, or is it possible to use every feature of .net equally well in either language? Cheers (and I know I'll be joining the dark side). :)
ChrisB ChrisDoesDev[^]
While I view VB syntax as a plague upon the industry (one of the reasons that stupid, ugly underscore "_" is back because VB syntax is so brain dead it does not understand case --- Opps.. Overflow... Rebooting and regainging control...), others are very devoted to it and the syntax to them is mere beauty. Even though the first langauge I learned was BASIC on a Commodore VIC-20 and did not really think I hit a decent langauge until I found C, VB for me is just a no go. That said, I still have to put up with it, like when I want to modify the DotNetNuke core, which they built with VB.NET or I write some MS Office macro, but I really do not like it. Back in the day, there were issues and many VB apps did not meet the quality nor performance of C/C++ apps along with their runtime. But in today's world of .NET, the languages are basically the same thing but with a different syntax. There are a few differences, but I doubt any would be considered show stoppers. So, if you like VB syntax or could picture yourself dealing with it every day, then no biggy, but if you really do not care for it and like C# or C++, then why bother, just find a job somewhere else that uses the tools you prefer. I mean, it is not like all jobs have switched to VB, there are tons of them for C#. Taking a job using a langauge or technology you really are not into is about like a Windows developer signing up for a Linux job, there is a lot of holes and you have to spend time learning at the cost of the employer. Life is short, get a job you like!
Rocky <>< Latest Code Blog Post: Linq - One-to-One issues? Latest Tech Blog Post: You got to see this - Seadragon and Photosynth!