For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
Hi, I have this old VB6 project that I need to modify a little. My question is where I can download(spyware free) VB6 or .ISO image? We do have MSDN subscription, but I can't find anything but the service pack. Found these installation instructions for Win 10: How to install Visual Basic 6 on Windows 10[^]
If you're saying "typical Microsoft mess", they've been screaming "get your apps moved to VB.NET" for the last 20 years.
VB6 IDE support ended in 2007(?) and is not supported on any current version of Windows. The VB6 runtimes will be supported until the end-of-life of Windows 11, currently, for the 22H2 version, in 2025.
Nobody can complain about it. They've had over 20 years to get the code moved over to .NET.
My question is where I can download(spyware free) VB6 or .ISO image?
And then you are going to run it on what? You would need an OS (windows version) which runs it and then a computer that runs that.
Hypothetically one of those links seems like it might be the CD image? Or the installer?
So then maybe you can create a VM that would run maybe Windows 95 or Vista? Then run the installer in that? But you would need to find Windows 95/Vista to install in the VM.
Myself this is why being a pack rat can be a good thing.
I am rather certain I have a computer tucked away with Windows 95 on it. (Never had one with Vista.)
I also have all the MSDN CDs/DVDs back to the 90s. (I think that means I have a developer version of Vista though.)
I even have some monitors which would be required for that computer. Although I have been thinking of tossing those.
We can use API to communicate two different applications.
I have one major doubt, that I am having my VB6.0 application need to integrate with third party webbased application.
Is this possible to use API keys through vb6.0 code to link with third party API?
This has nothing to do with the language being used. Yes, you can use the API keys, but it's your code and/or library that communicates with the API that's going to use the keys.
But, WHY ON EARTH ARE YOU USING VB6? It's been dead for 20 years now. New development in VB6 is a complete waste of time. You're going to end up rewriting this app sooner than you think. VB6 runtime support will end with the end of support for Windows 11. Support for the 22H2 version of Windows 11 will end in October 2025, just under 3 years from now.
Don't worry too much about people telling you that VB6 is outdated, dead, or both. There are millions and millions and millions lines of VB6 code out there, keeping companies running and being profitable. And if you have VB6 skills, you definitely have employment and earnings opportunities for many years to come. I should know: I am quickly approaching my 70th birthday, I am retired, and still bring home quite a bit of bacon by free-lancing, carefully selecting what I want from a ridiculous number of offers/requests.
Oh... when someone tells you that VB6 is outdated, dead, or both... just remind them of COBOL...
And to come back to your question: yes, VB6 can be used to interact with many API. Depending on the API, you will use different tools and/or techniques. Sometimes it will be more difficult than using other, more modern languages. In other cases, strangely, it will be easier. Go figure.
This just goes to prove the point that VB6 applications should be retired and rewritten into a more modern language. You have a limited future as a viable developer and you are able to be very picky about which jobs you take on. While there may be millions of productive lines of code out there finding a young developer to support it is a challenge.
Encouraging anyone to continue with VB6 is doing them a disservice.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
The useful life of a "typical" program is 5 years; obviously, you (and I) don't believe in typical.
(I'm not one of the respected ones).
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I