We help IT Professionals succeed at work.

VB Package Deployment -- Version Conflict with Riched32.dll

larkahn
larkahn asked
on
While I tried to understand some documentation at the Microsoft web site on this, I don't.

I am using VB6 with service pack 5; however, under the components, the RichTextBox is listed as being from service pack 4.

Using the setup program created by the VB Package and Deployment Wizard, a screen appears with the titlebar message "version conflict." The message on the screen is as follows:

A file being copied is not newer than the file currently on your system. It is recommended that you keep your existing file.

File name: c:\Windows\system\RichEd32.dll

Your version: 5.0.1458.47

The impression I got from the microsoft site was that I cannot update this file in VB 6 for installation programs. This is a potentially dangerous message to receive as an end user may mistakenly press "NO" which would in effect not save the more up to date file and install the file from setup whic is older.

Can someone clarify what is happening and how I can solve this so that the install program would automatically keep the more up-to-date version without a prompt. Is it possible?

Larry Kahn
Comment
Watch Question

Author

Commented:
I am using Windows 98 first version.
TimCotteeHead of Software Services
CERTIFIED EXPERT

Commented:
On your development machine you have certain versions of various files. These are included in the p&d installation package and deployed to target machines. On one or more of these machines a more recent version of one or more of these files exists. The p&d setup application sensibly warns you that this is the case and offers you the opportunity to keep the newer file or overwrite with the old one.

You have a couple of options:

1) Include advice to the users that will install your application to answer "Yes" to such questions.

2) Modify the setup1.exe using the project in the \program files\microsoft visual studio\vb98\wizards\pdwizard folder to not ask and always keep newer files.

1) is easy but not 100% reliable, 2) is more difficult but will achieve this end. The only downside is that if you application only works with a specific version of a component you may have problems. Alternatively though if other applications require the newer component then these will also stop working properly. The choice is yours.

Author

Commented:
Regarding the files that come with the P&D application package, are these the files that are in the Wizards/PDWizard/Redis folder? It's not possible to update, or in this case, the Riched32.dll them from the Microsoft web site?

2) definitely is more difficult and I'm not sure I would know how to do this, other than when the overwrite form loads, to have it automatically click the mfYes=true code.
TimCotteeHead of Software Services
CERTIFIED EXPERT

Commented:
Absolutely you could. The files in the redist folder are those which will be packaged with your application along with any from \windows\system32 or \winnt\system32 which are required. As you go through the p&d wizard it shows you which files will be included and where they come from. If you have the latest versions of all of these on your development machine then only the latest versions will be included and therefore deployed, thus avoiding the issue (providing your application still runs as expected).

Author

Commented:
Yet, the impression I get from the following article is that I cannot really replace my file 5.0.1458.47

http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q197580



CERTIFIED EXPERT
Author of the Year 2009

Commented:
Hi larkahn,
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will ask a Community Support Moderator to:

    Accept TimCottee's comment(s) as an answer.

larkahn, if you think your question was not answered at all or if you need help, just post a new comment here; Community Support will help you.  DO NOT accept this comment as an answer.

EXPERTS: If you disagree with that recommendation, please post an explanatory comment.
==========
DanRollins -- EE database cleanup volunteer

Author

Commented:
Dan, I feel my question, in particular related to the final clarification I asked, was not answered. Also, I think there was another possible answer which I hit upon by myself. Since there was a high probability that the RichEd32.dll file is located on most computers, one solution was to uncheck this file when creating deployment/setup package to make sure it wasn't even included in my final package. No one ever gave me this possible solution and was probably the simplest to implement.

My feeling is to close this question with no points awarded.
CERTIFIED EXPERT
Author of the Year 2009

Commented:
Thanks for the feedback.  Unless TimCottee feels strongly that he deserves points here, I'm changing my recommendation to:

   Refund points and 0-pt PAQ.

DanRollins -- EE database cleanup volunteer
TimCotteeHead of Software Services
CERTIFIED EXPERT

Commented:
I am not that desperate, and apologies to larkahn if I failed to keep in touch with this question.
Per recommendation, points refunded and question closed by
Netminder
Community Support Moderator