|
From my viewpoint it depends on what the code is for. I converted my VB6 programs to VB.NET over 20 years ago. Some things took very little effort as I was able to copy large chunks of code. I redid all of my forms from scratch, but I was able to reuse a lot of code.
Most of the code I have written involves controlling test equipment and taking measurements. I like VB.NET because it is easier for someone with very little programming experience to follow what the test code is doing.
|
|
|
|
|
[disclaimer: I supervise a varied codebase that includes a few large VB apps, with many thousands of lines of code.]
Interesting responses to this, ranging from funny to pragmatic to completely off-base.
You need to look at these as IT projects and define your timelines based on need. You didn't provide any details about what the apps are or how they are used, so it's hard to do a decent analysis. Short answer: I'd look at 5-6 year target zone. No sense on pushing it to the limits. Depending on the apps involved, the write could take a few years so starting sooner is better than later.
There is no "re-factoring"; this is a ground up, blank canvas rewrite for desktop apps. C# is the way to go but VB.net isn't terrible. But there's a lot of unknowns:
Are these just small apps serving limited functionality? Data connections and underlying database? Personally, I'm not a fan of migrating databases and codebase at the same time if it can be avoided. It interjects a ton of potential errors. Whether it's data first or code first depends on circumstancePrinting. Many old VB apps do a lot of document printing (not reports). They take a lot of code/time in .net OOP analysis. Meh. Not knowing the codebase, can't answer that one. It's not trivial, and it can be tough to flesh out because you're looking at the existing app. Like anything else, lots of thinking here. Web? Two pronged-question. In our review of some of the VB uses, web-based apps are a more suitable replacement than rewriting desktop apps. We have several going in that direction, though the back end remains in .net in some cases. The second piece is if the apps or data interact with the internet as that plays into the design. It boils down to the apps; how big they are and what they do. I'd start planning as soon as time allows. If you can transition functionality to a new program, it's not a bad approach. Avoid the light switch approach if you can.
|
|
|
|
|
That's an issue for my successor to deal with - I'm retiring in no more than 3 years from now, so I'll just keep going with VB.Net. The programs I'm dealing with were here before I was hired, and I have no doubt that they'll still be around after I'm gone, so I don't feel a pressing need to change anything.
|
|
|
|
|
As the subject says - Google is ending its programming competition. There will be a final round (without prizes or progression) and then they will be removing all trace that it existed.
Sad times - I enjoyed the challenge.
Oh well, there is still Meta Hacker Cup... for now.
|
|
|
|
|
RainHat wrote: Google is ending its programming competition.
Does it qualify to appear on KilledByGoogle.com?
(looking at that list...who would want to commit any resources to anything produced by Google? Seems like they have the attention span of a 2-year old...)
(And stinks just as much)
|
|
|
|
|
It is already there - under Google Code Competitons, along with Hash Code and Kick Start.
It seems the lifespan of any Google project is 6-10 years.
|
|
|
|
|
|
I am clearly developing the wrong kind of software.
|
|
|
|
|
cool
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
They manage straight talk (11)
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
DIRECTORATE - they manage
Straight - direct
Orate - talk
|
|
|
|
|
Yay !!! - YAUT - I was begining to think it was a badly written clue
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
I thought it was a good clue - just a bit
...
indirect.
|
|
|
|
|
*does a little dance*
After frustrating myself looking for algorithms to do anti-aliased rasterization of basic vector shapes like lines, ellipses and polygons and coming up largely empty I almost gave up.
Then I found nanosvg[^]. This is a library for doing vector graphics using SVG (Yes - that SVG the XML way to paint with geometry)
I hacked it to ribbons to get it to fit on little thumbnail sized computers, and am now happily rendering Scalable Vector Graphics using the htcw_gfx graphics library I wrote.
I still have a lot to do but the proof of concept is working quite well.
I mean, I was just hoping for some rasterizing techniques, and I got the whole ball of wax.
What's funny is they based their rasterization code off the same public domain code I am using to rasterize my truetype fonts. Github is apparently a small world.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I see a massive article on the horizon
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
honey the codewitch wrote: Worthy Github code is apparently a small world FTFY
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I'm honestly not really picky about what I find on github if it does something I previously couldn't do.
I figure for stuff like graphics and user interfaces code that works is better than no code at all.
Taking codebases under my wing, shoring them up, kicking the tires and all that is par for the course.
Sometimes it's worth it.
To err is human. Fortune favors the monsters.
|
|
|
|
|
honey the codewitch wrote: found nanosvg[^]. This is a library for doing vector graphics using SVG (Yes - that SVG the XML way to paint with geometry)
I hacked it to ribbons Wow !
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
|
|
|
|
|
#Worldle #403 3/6 (100%)
🟩🟩🟩⬜⬜⬅️
🟩🟩🟩🟨⬜⬆️
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
hard one had to use map
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
#Worldle #403 1/6 (100%)
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
Got in first attempt.
|
|
|
|
|
excellent
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
This map in memory thing is really good for one's brain.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
My Tiny True Type engine for LVGL uncovered a long standing but previously hidden bug in LVGL's POSIX filesystem caching subsystem.
Because of that the LVGL devs are banging on my library something fierce to tease the errors out so they can fix it.
And it's making me nervous, even though my code is holding up fine.
I should have included in the license: NOT FOR USE FOR ANY PURPOSE WHICH MAY MAKE THE AUTHOR ANXIOUS
It's being stress tested, and I'm the one who is stressed.
To err is human. Fortune favors the monsters.
|
|
|
|
|
This is a similar feeling to a parent moving their barely grown child out of the house.
Nothing much you can do.
Just hope the library doesn’t ask to move back home in 3 months!
|
|
|
|
|
As an aside, I've been hunting for rasterization code to handle complex anti-aliasing for basic vector shapes.
Couldn't find it, but I did find an SVG interpreter in C i ported over to my library. Anti-aliased everything. It's not full SVG, but it's a significant subset.
Not the fastest thing in the world, but good for simple designs, and is a pretty novel way to "skin" a user interface.
Pretty excited. I *just* got it working.
And all because I couldn't antialias a filled ellipse. ha!
To err is human. Fortune favors the monsters.
|
|
|
|