Basically, agree, but by somewhat different reasons.
Yes, VB.NET is similar in features compared to C# but always goes behind. Microsoft just does not take VB.NET as seriously as the flagship of C#. Other problems are more serious: VB.NET would be a pretty bad investment. First, C# and C++/CLI go through strict standardization under ECMA and then under ISO, but it never happens to VB.NET. I cannot believe it might ever happen in future.
There is one more reason, the social one. The fact is: many developers considering themselves at least "professional" do not take anything named similar to "VB" as "real". The historical reasons just do not matter (VB earned bad reputation with both quality and popularity with poor developers, and whatever else), this is the real attitude of real people. This is not for the flame wars or something like that. I'm trying not to express my own attitude; this is just a "medical fact", fact of nature.
In fact, if you try to find an answer of some technical question in .NET, best answers are usually in C#, and much more finding on most difficult topics will appear in C#. So, a serious VB.NET developer should also understand at least some C#.
By the way C++/CLI is a powerful thing which should be taken into consideration. I can see some drawbacks in it (I used to discuss on CodeProject pages). For example, I saw Microsoft article where they explained that it has its special optimized instead of general-purpose .NET optimizer used with other compilers. Mixed mode and value (stack) semantic for reference type are unique to this language (not counting IL).
I've been doing this for a LONG LONG time. I really don't need the history lesson on why VB has the reputation it does.
Also, Microsoft DOES take VB.NET seriously and it shows as the feature sets between C# and VB.NET have been merging quite a bit and continues to [ut considerable resources into adding features concurrently into both languages. And with .NET 4.5, VB.NET will get a feature you can't have in C# yet. I'll let you squirm on what that is for a while while I go try to remember what it was!
All I was refering to in this thread was that VB.NET doesn't support pointers, which makes image processing quite a bit easier.
May be I'm wrong, but I feel you are overreacting about "history lesson", saying as if it's something bad. What's wrong with lessons? As you probably know this history better then I do (mainly because I never allowed myself to play with the idea of accepting the opportunity to work with VB), you can always tell us something more interesting and useful than I could. And correct me if I'm wrong. I've noticed a long time ago that reading your posts can be really useful; as that can give a chance to learn something, and I'm trying not to miss a lesson, even if I think I know things the best way — but I always can be mistaken, like probably all of us. Perhaps it's good to remember that if I reply to your post, it does not mean that I always address personally to you. Everyone can read our conversation.
Thank you for interesting discussion. Will talk to you later.
I hope we are good. And we are doing basically the same thing on this site for this community. As to the criticism and possible negative estimates or votes, they are normal, absolutely unavoidable in any truly creative environment, as well as our mistakes, and they can be and should be handled in productive and constructive ways.
No, we're good. If I was pissed at you, I'd just ignore you.
As to the criticism and possible negative estimates or votes, they are normal,
absolutely unavoidable in any truly creative environment, as well as our
mistakes, and they can be and should be handled in productive and constructive
Sorry if I'm jumping in here but I thought the conversation was interesting, I have worked with diehards of both language conventions. Both had valid reasons for their preferred environment.
But if I may, as a programmer that started writing software using Clipper (way back when, but late in life mid 40's and now nearing retirement) then progressed to VB4-6 and now VB.Net may I suggest that VB was for me an easier language to learn, and more importantly correct me if I'm wrong. One can create a working application very quickly using Visual Basic.
It's been a long time since I have to anything to do in C mainly because the company I work for uses Visual Basic as it's preferred programming environment.
I fully agree; even if I knew a way to determine something like that, I'd probably go for the functional test anyway. With external dependencies involved, I prefer to eat the pudding, rather than to look for the boxes.
Shouldn't be hard to figure out what to put in the Up/Down Button click handlers. You'll probably also handle the MouseDown/MouseUp events on those if the user wants to change the numbers without clicking for each increment.
Then the UserControl just exposes the time as a property. The gettor just puts a datetime object together based on the values in the textboxes. The settor does the opposite.