VB.NET
-
Shog9 wrote:
For the last few months, i've been enhancing and maintaining a library written in VB.NET. I've done a lot of other stupid, miserable things during this time, but this library pretty much takes the cake in terms of filling me with shame and self-loathing at the end of a long day.
So why didn't you just rewrite the thing?
The Grand Negus wrote:
So why didn't you just rewrite the thing?
Well, i am, a bit at a time. But technically, i'm not supposed to be spending all that much time on it - the original plan was, i'd take over ownership of it, but any work would be done by outside consultants, thereby freeing me up to work on more interesting projects. So... now i'm slowly learning to program consultants. In the meantime, there's still work that needs to be done...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
The Grand Negus wrote:
So why didn't you just rewrite the thing?
Well, i am, a bit at a time. But technically, i'm not supposed to be spending all that much time on it - the original plan was, i'd take over ownership of it, but any work would be done by outside consultants, thereby freeing me up to work on more interesting projects. So... now i'm slowly learning to program consultants. In the meantime, there's still work that needs to be done...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
Shog9 wrote:
So... now i'm slowly learning to program consultants.
Big job. What language are you using for that? :)
-
For the last few months, i've been enhancing and maintaining a library written in VB.NET. I've done a lot of other stupid, miserable things during this time, but this library pretty much takes the cake in terms of filling me with shame and self-loathing at the end of a long day. It's somewhat akin to knowingly feasting on mudpies, all day, for weeks at a time...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Is there any reason you can't convert it to C# ? Excellent tools exist for this purpose.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
Is there any reason you can't convert it to C# ? Excellent tools exist for this purpose.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
Other than the one you illustrated below? ;) It's not the syntax that really irritates me; it's the little programming techniques that, by now, just scream "VB" to me: insufficient error handling, massive amounts of duplicate code, unnecessary use of late binding, etc. Every time i need to make significant changes to a class or routine, i'll re-write it, to where it reads the same as it would have if i'd written it in C#. Eventually, i'll either have re-written the whole thing to where converting it to C# will be painless... or i'll have pushed the project off onto some other poor sucker, and won't care anymore...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
Other than the one you illustrated below? ;) It's not the syntax that really irritates me; it's the little programming techniques that, by now, just scream "VB" to me: insufficient error handling, massive amounts of duplicate code, unnecessary use of late binding, etc. Every time i need to make significant changes to a class or routine, i'll re-write it, to where it reads the same as it would have if i'd written it in C#. Eventually, i'll either have re-written the whole thing to where converting it to C# will be painless... or i'll have pushed the project off onto some other poor sucker, and won't care anymore...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
You do have "Option Strict" on?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
You do have "Option Strict" on?
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
It's set up to warn. Eventually, i'll manage to clear up all the warnings... :sigh:
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
-
Is there any reason you can't convert it to C# ? Excellent tools exist for this purpose.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
In my experience, the language used and the options set to the strictest of standards still doesn't prevent people from writing bad code. Phil
I agree. It sounds like the original code was written in .NET "VB6 procedural" style, and not leveraging any of the benefits provided to VB developers through .NET. It's an unfortunate side effect of people not upskilling their techniques with the move from VB6 to VB.NET.
-
For the last few months, i've been enhancing and maintaining a library written in VB.NET. I've done a lot of other stupid, miserable things during this time, but this library pretty much takes the cake in terms of filling me with shame and self-loathing at the end of a long day. It's somewhat akin to knowingly feasting on mudpies, all day, for weeks at a time...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Haha. I hate to say this, but in my career, I keep coming across projects that are mostly C# with a small percentage of awful VB.Net code. (I do find GOOD VB.Net code on the 'net.) For example, in my first job out of college, 95% of the code was in C#. There was one group of dlls written in VB.Net where the developer had all methods take a single array of objects as THE argument. Even weirder was that almost all of the values being passed on the stack belonged as object-level fields. The code was an example of how NOT to use weak typing. It was very clear to me that the original developer spent a few months on the code... I re-wrote it all (from scratch) in 3 days!