|
actually .... NO
well it could, the programmers before him are to blame
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Well I know the C based languages better, I have done some nasty things with VB for which I am now eternally sorry for. It just that the boss man's "well its basic it can't be that hard" attitude with vague requirements, just make it work as it did before with these changes (That's the problem, it didn't!)
|
|
|
|
|
This has nothing to do with VB. It has everything to do with the morons who came before you.
I hate the entire C(whatever) is better than VB war altogether. I get paid to write code, period. It doesn't matter if it's Assembly, C/C++, C#, VB.NET, VBScript, or whatever. It's all the same to me.
|
|
|
|
|
You are right, of course.
|
|
|
|
|
Having used both in an enterprisey fashion, I can say that C# is better.
VB makes bad coding too easy. But, used properly, it's not too horrible.
|
|
|
|
|
PIEBALDconsult wrote: VB makes bad coding too easy
Have you seen the crap the noob's are writing in the C# forums??
|
|
|
|
|
Yes, but they seem to make an effort of it!
|
|
|
|
|
True!
|
|
|
|
|
So, the issue isn't that you hate VB, it's that the people who preceded you left a stinking pile of crapola. Honestly, I don't understand why there is such a hatred of dislike - it's people who make stupid code - not the language. It's just as possible to write stupid code in C# or Java or C++ (insert language of choice here) as it is in VB, so it's pretty pointless blaming the language.
|
|
|
|
|
True, but the programmers have access to high powered rifles (I know for a fact one was a US Marine Sniper) It's safe than naming names!!!
|
|
|
|
|
glennPattonWork wrote: I know for a fact one was a US Marine
Ah, there's your problem.
If your neighbours don't listen to The Ramones, turn it up real loud so they can.
“We didn't have a positive song until we wrote 'Now I Wanna Sniff Some Glue!'” ― Dee Dee Ramone
"The Democrats want my guns and the Republicans want my porno mags and I ain't giving up either" - Joey Ramone
|
|
|
|
|
I didn't read the post, but from the title, I understand your pain.
|
|
|
|
|
I assume that if it was Delphi your title would be "I hate Delphi, I hate Delphi & I HATE Delphi". If it was C++, C# or Java?
It looks like you are facing what I call "legacy mess" that does not necessarily translated to a specific language (OK, in your case is VB). Believe me, I feel the "pain", but on the other hand there are still a lot of companies (of any kind) that operate with legacy software (even VB) without a problem erroneous code.
I would say that the real tragedy is to see nowadays projects mimic "legacy styles" (including code and people) like the ones you try to deal with.
I wish you the best, in other words not to deal again with mess.
Cheers
|
|
|
|
|
It's just that if I was given the go ahead I could have written a scalable, neater version in C# quicker than this elephanting mess is taking...
|
|
|
|
|
I would rather sort out some bad VB than bad assembler.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
|
Yes On Error Resume Next and my favourite
On Error GoTo ErrorHandle
ErrorHandle:
'**** this (stars to make KSS safe)
Application.DoEvents
to quote Dave Borman 'My God It's Full of Stars'
|
|
|
|
|
Don't blame VB - it has it's rights...
The problem - IMHO - is that the developers(?) before you made wrong decisions and left you with a pile of sh...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
|
|
|
|
|
True, very true, but as I said above they have access to weaponry and VB (as far as I know) can't kill me!
|
|
|
|
|
Truly - the worst developer work is to renovate others code...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
|
|
|
|
|
I 'dunno, I kind of like VB. My career really got it's boost with VB6. Interestingly enough I still get projects where they want VB.NET or for VB6 application maintenance and I don't mind it.
But I admit with all of my new projects starts, I've been using C# for PC side development and have grown more comfortable with it.
It was broke, so I fixed it.
|
|
|
|
|
Point, when you were learning it was great. When you want something quick to try an idea it has a place. A production environment running a test rig, no, just no! VB like everything has its place...
|
|
|
|
|
glennPattonWork wrote: A production environment running a test rig, no, just no!
Why not? By the time the code is run, it is exactly the same CLR as a C# application (that is what puts the "common" in Common Language Runtime) executing exactly the same code in the .NET Framework.
Sloppy coding is sloppy coding, and C# can be as bad as, even worse than, VB.
|
|
|
|
|
Most my production VB code is still in use and have had little or no issues.
What issues do crop up they are generally having to do with adding features for new product, updating the UI of the applicationor changing test parameters. I've offered to rewrite them into C# code, but the answer is always, Why? If they still work, lets keep using them.
VB if coded well is a very viable platform to use, it's not just a "Starter" language although it does serve well in that capacity. The problem with VB is the ability to abuse some of the features, things like resume next and goto. But those features are great tools when debugging or running code that you know is incomplete. These have their place.
I've have seen some truly awfull code in C++, C#, assembly you name it. Any language can be abused it's not specific to VB.
It was broke, so I fixed it.
|
|
|
|
|
for the honesty. My career has followed a similar path. The 'legacy' VB6 applications still install and work fine on Windows 8, but most importantly, they continue to generate revenue in sales and support contracts. Like you, new projects are either C# or VB.NET.
"Go forth into the source" - Neal Morse
|
|
|
|