|
-
Sep 4th, 2009, 12:53 AM
#1
Thread Starter
Addicted Member
Version Conflict
Hi 
I created an installer for my program using Package and Deployment Wizard.However when i tried to install it i received the following message:
conflict version
a file being copied is older than the file currently on your system.it is recommended that you keep your existing file
Pls.check attachments:
Attachments removed at OP request
The program runs perfectly, but i want to fix this Version Conflict.
Thanks!
Last edited by Hack; Sep 15th, 2009 at 05:54 AM.
-
Sep 4th, 2009, 02:24 AM
#2
Re: Version Conflict
This is quite a common error with the P & D Wizard 
if you were to use a different installer ( Like Inno Setup ), you shouldn't have this problem
VB.NET MVP 2008 - Present
-
Sep 4th, 2009, 04:24 AM
#3
Re: Version Conflict
I dont think theres need to deploy SHDOCVW... is there?
That is for the webbrowser control.. yes ?
_____________________________________________________________________
----If this post has helped you. Please take time to Rate it.
----If you've solved your problem, then please mark it as RESOLVED from Thread Tools.

-
Sep 4th, 2009, 12:21 PM
#4
Re: Version Conflict
Moved To Application Deployment
-
Sep 4th, 2009, 02:21 PM
#5
Re: Version Conflict
This is a system component that is serviced as part of IE, updated via Windows Update. You do not deploy it, the user must install IE. The PDW is smart enough not to try to include it in a setup package on its own. Some people think they know best, resulting in an error like this one.
Either you forced its inclusion or your PDW's VB6DEP.INI has been corrupted. This DLL is normally the first entry in its [Do Not Redistribute] section. It might be missing if you haven't applied VB6 SP6. In general the VB6 developer is responsible for maintaining VB6DEP.INI because VB6 has been in a degenerate state of support for many years (and not at all now).
PRB: Shdocvw.dll Is Not Included in PDW Setup Package
Third party legacy installers are strictly "at your own risk" affairs. Hopefully that Inno thing addresses this particular issue rather than going ahead and trashing a user's OS by installing the version-mismatched DLL. Thankfully (beginning with Vista) Windows is more aggressive about protecting this DLL now.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|