|
As I see it VB6 is the same as visual basic for applications. So as long as they are going to support VBA it seems logical Microsoft will have to support VB6.
My concern is that the Microsoft people are not merging VB.net nominclature with C#. They share the same code base now, so why not upgrade the editor to handle both syntax in one environment. That way there would never be a need to retire either one. Computers are powerful enough to support that structure now which may not have been the case years ago.
I prefer personally "if then ....... end if" for tracing purposes over the c# equivalent which ends everything with a }. Nested loops with everything sharing the same ending are much more difficult to debug. Thank you.
|
|
|
|
|
Visual Basic stopped working with Windows 7. Microsoft dropped a bunch of required modules in Windows 7. The solution was to add these modules to the VB6 build. Again with Windows 10, Microsoft did the same thing, requiring modules to be included in the build. In addition, Microsoft changed the registry structure/contents on Windows 10. I am still trying to code replacement to find the full path to installed programs.
Years ago, I was going to convert my VB6 programs to VB.net, but ran into big problems as the form handling routines did not have the same capabilities of VB6. That was probably 18 years ago, so I can't remember the details now, but I'd guess, and it is only a guess, that things like <controlname>_LostFocus no longer worked and I didn't want to waste the time on how to get around the problem. As I recall, there were a lot of deficiencies with VB.net. With changes in Windows 10 and Windows 11, I may have to re-write all my applications in a new language. I've been retired for over 10 years, so I don't think that is going to happen. Microsoft sucks!
And don't get me started on the 'unknown publisher' message that comes up every time I run an application on Windows 10. Microsoft doesn't want to make things easy for the developer anymore.
|
|
|
|
|
I wrote a Software Defined Radio in VB6 + Delphi + Assembler back in 2003, and it's still in use today - I still see downloads - https://www.g8jcf.uk/. The Delphi & Assembler were used to write the low level DSP and vector arithmetic - it was developed on a Celeron 333 with 192 MBytes of RAM a SONY VAIO laptop !!!
The G8JCFSDR is a hobby program for free for a relatively small base, so it's not worthwhile me porting it to C#, although it might be an interesting excercise.
Back in 2003, so much stuff had to be added around VB6 to hook message events, handle callbacks, etc, so it might be much easier/quicker today
Ah those were the days 
73
Peter - GM8JCF
|
|
|
|
|
LucidDev wrote: Microsoft doesn't want to make things easy for the developer anymore.
Presumably you are referring to the Basic domain only because as far as I know Microsoft never had an actual vision to make any easy for developers. It was always about the money.
|
|
|
|
|
Yes, you are correct. My comment was based on MS saying they would continue to support VB6 until..... VB6 is not supported 'as is' on current OSes. After adding in missing support modules in the build and installation process, applications could run for the most part on Windows 10. Some clients complain that the code does not work on Windows 11, but I don't have a Windows 11 system to test it on. I use Visual Installer to build my install files and asked them to test an install on Windows 11. They said it installed fine, so I don't know why one client had a problem.
Another technical problem is that before Windows 10, you could get the full path to an executable by going to the registry entry "HKLM\software\microsoft\windows\currentversion\app paths\<programname>" where <programname> is the file name of the application, like "Outlook", for example. Not anymore!
|
|
|
|
|
LucidDev wrote: you could get the full path to an executable by going to the registry entry
No that is not true as stated.
If you 'installed' it then it was true. And apps specific to Windows itself were all installed so they would show up there. Well at least once that really started to be used. Not sure how that wouldn't still be true because I think that is needed for the 'uninstall' to work from the Programs applet. Perhaps they moved it.
I just checked on Windows 10 and I see Outlook is still there. Since individual components would independent maybe they have moved some but not others.
|
|
|
|
|
In Windows 10, all of the installed applications are located in this registry key:
"HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store\"
Unfortunately, I have not been successful in searching or storing the data to search for the application I am looking for. One of the suggested solutions was, as you imply, is to look for uninstall information. Unfortunately, not all applications can be located using this method.
My point is that MS said that VB6 would continue to be supported, but they keep changing the OS making that impossible. If you happen to have code that can read the referenced key into an array, I would appreciate seeing it! Thanks.
|
|
|
|
|
Ah...I was thinking you meant it was being kept is some completely different storage mechanism.
At any rate for any new major OS version you must always fully regression test it. And then adjust for differences.
Maybe VB was hiding that at some point but perhaps more likely is that the dependencies you had your app(s) just didn't move between major versions for a while. So you got lucky. Now they moved so you must adjust.
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
