[RESOLVED] Msvcrt.dll

[matrik02]

Should I put this files (Msvcrt.dll) in the installer package if I want to deploy my program to target machine that used window XP ?

Should I deploy this files scrrun.dll ?

I don't want to deploy my program on target machine that used other then Windows XP . So it this files already exist in Windows XP ? it this files is already exist on every OS that used XP, I will not include this files. I have read from this link, but I not much Understand http://www.***********/installerproblems.html. What it mean with VB 6 Runtime Files ? it is exe files or dll files?

[si_the_geek]

Based on your other thread, these files haven't been added to your package by P&DW, so why do you want to add them?

You should only be adding files that are required by your program (or files that those files require), as anything else will make your package bloated, and possibly cause problems for the computers that your program is installed to.


I'm not certain about scrrun.dll , but am sure that Msvcrt.dll should not be included.

[dilettante]

You may find BUG: Distribution of Microsoft Scripting Runtime Library Fails informative.

Also look at PRB: Your Computer Does Not Restart After You Install a Microsoft Visual Basic 6.0 Application That Includes a MSVCRT.dll File.


Basically these are both files you should not try to redistribute. They exist in OS-specific versions and you could wreak havoc on downlevel systems that do not protect system files aggressively as WinXP, 2003, Vista, and 2008 do.


You might also want to read Best practices for deploying Visual Basic 6.0 applications which toward the end identifies the core components of the VB6 runtime. XP Gold ships with these, and SP1 and SP2 each update them, but not to the most current versions (VB6 SP6b).

[dilettante]

You also seem to be trying to deploy MSADO27.TLB based on your other thread here. This is not a good thing to do in general. If you must deploy MDAC components you should do this via MDAC_TYP.exe which the PDW should offer to package for you.

Of course you'll want to update the MDAC_TYP.exe in your PDW's "redist" folder in order to package the right one. Generally you shouldn't deploy MDAC anymore anyway except on downlevel OSs (prior to Win2K).

You can look into options in BUG: Error "Unable to Register MSADO15.TLB" If You Use a PDW Package to Install a VB Application.

Also look at How To Control Which MDAC Version the Package and Deployment Wizard (PDW) Distributes.

[randem]

If your app does not require the Scripting Runtime Files ... Do not deploy them... as well as any other files your app does not use. How ever if your app uses scrrun.dll do not deploy this file alone. You need to deploy the whole scripting runtime installation for the target OS.

[matrik02]

I don't deploy this files in OS XP and it work now. But I unsure if the program works or not If try deploy the package in OS 2000 if I don't included that package.

I don't know the whole scripting runtime. Where I can get this list?

[Hack]

I don't deploy this files in OS XP and it work now. But I unsure if the program works or not If try deploy the package in OS 2000 if I don't included that package.

Test it out on a 2000 machine before you deploy it.

[randem]

Why do you think you need the Scripting Runtime and what about that document you read caused confusion?