<div>
remove the lines of these DLLs from setup.lst
</div>


remove the lines of these DLLs from setup.lst

<div>
No, I want it to install these but only when they don't exist on the installed machine.
</div>


No, I want it to install these but only when they don't exist on the installed machine.

<div>
these 2 files will exist because they are installed with all Windows installation.
</div>


these 2 files will exist because they are installed with all Windows installation.

<div>
PS: In my particular instance, COMCAT.DLL version 4.71 is in my redist folder, version 5.0 is in my system folder. &nbsp;OLEAUT32.dll ver 2.40.4275 in redist, ver 2.40.4518 is in system.<br />
My installs generate [Bootstrap Files] section in setup.lst referencing the older redist versions every time!
</div>


PS: In my particular instance, COMCAT.DLL version 4.71 is in my redist folder, version 5.0 is in my system folder.  OLEAUT32.dll ver 2.40.4275 in redist, ver 2.40.4518 is in system.
My installs generate [Bootstrap Files] section in setup.lst referencing the older redist versions every time!

<div>
Thanks, I was a pulling in an oleaut32.dll v3.5
</div>


Thanks, I was a pulling in an oleaut32.dll v3.5

<div>
<div class="content wysiwyg-content">
Is it possible to easily prevent the VB6 OLE and Automation files from overwriting the files if they already exist on the machine? I know it only writes with newer versions of the files. But I am having problems with newer version of these files preventing other 'critical' programs from working correctly on users machines.<br />
&nbsp;<br />
Specifically the oleaut32.dll, but in the past I have had problems with comcat.dll.<br />
<br />
I think at this point I'd rather have it not install these files and risk my program not running than to have the complaints.<br />
<br />

</div>
</div>


Is it possible to easily prevent the VB6 OLE and Automation files from overwriting the files if they already exist on the machine? I know it only writes with newer versions of the files. But I am having problems with newer version of these files preventing other 'critical' programs from working correctly on users machines.
 
Specifically the oleaut32.dll, but in the past I have had problems with comcat.dll.

I think at this point I'd rather have it not install these files and risk my program not running than to have the complaints.



Package and  Deploy Wizard dll version control problems

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.