VB 5.0 and Windows Vista

Hello, thanks to this forum I have come to know that the VB6 runtime files will be included in Windows Vista.

When I produce shareware programs for the Italian market, I normally use VB5 instead of VB6. The reason is quite simple: the VB5 runtime is present in Windows 98, Me, 2000 and XP, whereas the VB6 MSVBVM60.DLL is missing under Windows 98. Consequently, using VB5 allows me to avoid distributing the runtime even under Win98.

Now, I know that Windows Server 2003 does not include MSVBVM50.DLL, so I am obliged to distribute that library when targeting that version of the OS.

My question is, is MSVBVM50.DLL included in Windows Vista or not?

TIA

What's the big deal with distributing VB Runtime files? It's a safety measure and I would think that for the people that use your program you would want to be as safe in the distribution as possible to insure that your app worked properly. It's not like they add lots of size to the package. I don't get it????

Exactly, If your using a package and deploy app like Inno Setup, which i highly recomend then it will collect all the runtime files needed, and allow your user to safely load them on to their machine.

Use this with Inno Script, which will load up a VBP file and list all the components needed.

ILMV

I didnt visat was going to support anyhting but .NET? Did this change?

The reason why I prefer to avoid distributing the runtime is, some customers may not have administrative privileges on their machines, so they would be unable to install my applications.

The second reason is that some of my applications are to be used in a LAN, without any installation. Each workstation should only have a link to a shared folder, where my app is located, and launch the executable from there.

Unfortunately, I don't have the beta version of Windows Vista and I don't know if MSVBVM50.DLL is present in the System folder.

Can anybody check whether the "incriminated" library is shipped with Windows Vista in the System directory?

TIA

Quote:

---

Originally Posted by Pino

I didnt visat was going to support anyhting but .NET? Did this change?

---

I have read Windows Vista will be based on the same API as WinXP, so there shouldn't be any backwards compatibility problems. The .NET Framework 2.0 should be included in the OS, though.

have they changed that because origionally vista was not going to be compatible with any apps pre .Net?

Quote:

---

Originally Posted by Pino

have they changed that because origionally vista was not going to be compatible with any apps pre .Net?

---

I think MS realized that, by abandoning the COM technology, they would have shot themselves in the foot. People do not upgrade just for the sake of upgrading and that price would have been too high for customers to pay.

esposito,

Quote:

---

Originally Posted by esposito

The reason why I prefer to avoid distributing the runtime is, some customers may not have administrative privileges on their machines, so they would be unable to install my applications.

---

That really doesn't make much sense being that if you use any components or references that include dll's or ocx's you will have the same issue.

Quote:

---

Originally Posted by randem

esposito,



That really doesn't make much sense being that if you use any components or references that include dll's or ocx's you will have the same issue.

---

That's the whole point. I don't use any OCX's, references or third-party DLLs in my applications. You can get advanced functions by exploiting the Win32 API instead of using external libraries.