For the first time ever
-
Yer noting "he's a senior programmer/manager" and (later) that he's worked for the company for 27 years, both implying he's aged. And you have your CP profile pict set to an aging Clint Eastwood. Uh-huh. Interesting...!
~ [Don't] Visual[ize the] Basic[s], C#[ly instead] ~ ASPX: Apple Simply Performs eXcellently
Nice try. I'm not even 40 yet.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) -
I have been tasked to re-write an app in VB.Net I have never used VB.Net in my life. I created my first solution this morning and all I have to say is... :omg: :wtf: did I just get myself into.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) -
I haven't done anything major; but have used http://www.tangiblesoftwaresolutions.com/[^] for c# to vb conversions in the past. It converts projects not just code snippets.
-
I have been tasked to re-write an app in VB.Net I have never used VB.Net in my life. I created my first solution this morning and all I have to say is... :omg: :wtf: did I just get myself into.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)And the problem with this is? There is no good reason to choose C# over VB or VB over C#. It all comes down to whether you prefer IF .... THEN ... ELSE ... END IF or IF .... { ...; } else { ...; } I have yet to find anything that you can do in one language that you can't do in the other. I prefer VB simply because of my background (PL/I), but this is nothing more than my personal aesthetic preference. To argue that one is better than the other is merely religious bigotry.
-
And the problem with this is? There is no good reason to choose C# over VB or VB over C#. It all comes down to whether you prefer IF .... THEN ... ELSE ... END IF or IF .... { ...; } else { ...; } I have yet to find anything that you can do in one language that you can't do in the other. I prefer VB simply because of my background (PL/I), but this is nothing more than my personal aesthetic preference. To argue that one is better than the other is merely religious bigotry.
RobertBarnes wrote:
To argue that one is better than the other is merely religious bigotry.
I guess I'm a bigot then.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) -
It's very hard to make older people learn something new, that's probably why the senior guy will resist moving to C#. On the other hand, you can throw real arguments against going to VB.Net. To mention a few: 1 - Going from C++ to C# is a much more fluent approach. 2 - If the company has more stuff based on C#, it means it has more C# skilled people and that means there are more resources if they are needed. Reduced dependency on the VB.Net guy. 3 - There are a lot more resources on the web for C# language than for VB.Net. This minimizes the need of reinventing the wheel or having to translate everything. As proof you can just perform a search of C# vs VB.Net articles on codeproject, you'll see that there are a lot more articles on C#. There are a lot more arguments to favor C#, but I don't want to get religious about it.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
Fabio Franco wrote:
It's very hard to make older people learn something new
... what nonsense. The older we get, the more adaptable we become, as in reality there's really very little that's really "new". We've probably seen it before (and maybe written the compiler for it!) when it was new the first time around. However, the older we get, the less concerned we are about adding new buzzwords to our CV, as there's increasingly little likelihood we'll ever be touting our CVs around again. Thus we may not be quite so keen to jump on the latest bandwagon, and use a slightly more reasoned approach for adopting any new technology / language / toolset etc. It may very well be that this reasoned approach includes considerations such as "I've used it for years and am extremely capable with it"; "it's been around long enough for most bugs to be ironed out"; "it's been around long enough for a sizeable community of support to build up" etc.. etc.. but I would count these as perfectly valid and sensible approaches to throw out one approach in favour of a newer one. What I would point out though, is that as the O.P. has just rewritten the Borland stuff to VB.Net, he now obviously "knows" VB.Net and has just therefore removed one stumbling block to converting to it. There are now TWO vb.net developers in the department, instead of just one.... :laugh: Derek TP
-
Fabio Franco wrote:
It's very hard to make older people learn something new
... what nonsense. The older we get, the more adaptable we become, as in reality there's really very little that's really "new". We've probably seen it before (and maybe written the compiler for it!) when it was new the first time around. However, the older we get, the less concerned we are about adding new buzzwords to our CV, as there's increasingly little likelihood we'll ever be touting our CVs around again. Thus we may not be quite so keen to jump on the latest bandwagon, and use a slightly more reasoned approach for adopting any new technology / language / toolset etc. It may very well be that this reasoned approach includes considerations such as "I've used it for years and am extremely capable with it"; "it's been around long enough for most bugs to be ironed out"; "it's been around long enough for a sizeable community of support to build up" etc.. etc.. but I would count these as perfectly valid and sensible approaches to throw out one approach in favour of a newer one. What I would point out though, is that as the O.P. has just rewritten the Borland stuff to VB.Net, he now obviously "knows" VB.Net and has just therefore removed one stumbling block to converting to it. There are now TWO vb.net developers in the department, instead of just one.... :laugh: Derek TP
My OP, was a bit too short to make a point, see the post above yours with a more argued reply. In any case, I don't really think older people become more adaptable, they simply know more and can handle more situations. I don't really think the new is the strongest characteristic of elder people. That's a fact any neurologist will confirm. A child is much more likely to learn how to use a computer than an elder. Given these are completely new to both.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
I have been tasked to re-write an app in VB.Net I have never used VB.Net in my life. I created my first solution this morning and all I have to say is... :omg: :wtf: did I just get myself into.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)Well, at least it's VB.net, you still have the full power of the framework and full OOP; it could have been VB6! X| Probably someone else has already suggested it (I didn't read the whole thread), but you could write in C# and use Reflector or some similar tool to turn code to VB.net syntax ;) Another positive trait (IMHO) is the availability of the with statement. I really like it a lot ;) Good luck! :cool:
-
I have been tasked to re-write an app in VB.Net I have never used VB.Net in my life. I created my first solution this morning and all I have to say is... :omg: :wtf: did I just get myself into.
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)Write in C# and use a converter to convert to VB.NET InstantVB from tangable software does a great job, has a free demo version, and has a reasonable price. I use it (and InstantCS) to move between VB and C# on whim. There are other converters that handle common stuff well (sharpDev is a free VS replacement)
-
Well, at least it's VB.net, you still have the full power of the framework and full OOP; it could have been VB6! X| Probably someone else has already suggested it (I didn't read the whole thread), but you could write in C# and use Reflector or some similar tool to turn code to VB.net syntax ;) Another positive trait (IMHO) is the availability of the with statement. I really like it a lot ;) Good luck! :cool:
I started my programming adventures with VB6. VB.Net syntax and language is so different in style then C#; we all know this. I am not saying VB.Net is any less powerful or great. I am just not familiar with it. Things are already coming back to me from the VB days. Like I said before. I can complain, kick and scream, but I have a job to do and it must get done to specifications. Thanks for the reply. :)
Just along for the ride. "the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)