By reading the article http://www.microsoft.com/whdc/hwdev/driver/sfp/wfp.mspx, it seems to me that some MS system files such as msvcrt.dll should never be distributed by any company except MS. Where can I get a list of those files?

Thank you for any help.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you want to make your own list you can just build a clean build PC with the OS you are using and then make a listing of the System32 folder dll's ocx type files. You really shouldnt install ANY of those files with your apps.

Depending on your environment you may also want to include any files in the Office version your are using and also IE files should not be included.
Answered 03/21/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
Hi MSIMaker,

If I understand correctly, many Microsoft files are not distributable or not redistributable. For those files, how does an end-user obtain them? I guess the end-user can get those files by the following ways:

1. installed by OS, service packs, hotfixes, security patches, updates
2. installed by other MS products
3. installed by an non-MS products using msm provided by Microsoft
4. installed by an non-MS products using files obtained from special MS exe such as VCRedist.exe provided by Microsoft
5. installed by an non-MS products using msm provided by installation authoring tools such as InstallShield
6. installed by an non-MS products using objects supplied by installation authoring tools such as InstallScript Objects in InstallShield

BTW, what is the difference between not distributable and not redistributable?


Thank you for your help,

Peter
Answered 03/30/2004 by: pcwc66
Senior Yellow Belt

Please log in to comment
0
I have always thought that non distributable files were system32 OS installed files. I think we refer to them in different ways.

Most vendors will that are not packaging their software as msi files will use other methods to compile the installation and those tools tend to remove the thinking process from the author....and thats the dangerous bit.

They compiler will include ALL dependent files for the application......even System32 files and their associated registry entries. Because the compiler will always assume that the user will need those files.

In most cases the user wont need the msv*.* files if they have installed MS-Office or IE 6.x. They will need older runtime files but you can silo them to the app folder.

You really have to look at each app and who is going to use it. If you have 2 business units that use one app and only 1 business unit gets Ms-Office then you might be forced to deliver the files to both but with a "not overwrite" file set.
Answered 03/30/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity