Deployment Condition Statement for checking File Version?

  • Thread starter Thread starter Don
  • Start date Start date
D

Don

I've added a Setup and Deployment project to my Visual Studio 2005 Windows
Application solution and have several OCX and DLL files that will be
installed. But I can't seem to find any examples in the Help and
Walk-Throughs that show the syntax for the Condition Statement I need to set
in File Installation Properties to keep the Installer from overwriting
existing files unless the Date/Time and Version are older. I'd appreciate
any examples or links to examples. Thanks!
 
Hi Don,
But I can't seem to find any examples in the Help and
Walk-Throughs that show the syntax for the Condition Statement
I need to set in File Installation Properties to keep the Installer from
overwriting existing files unless the Date/Time and Version are older
Click to expand...

1. Add a File Search item, click main menu View | Editors | Launch
Conditions, then select 'Add File Search' on the 'Search Target Machine'
node.

2. In the new added File Search's item Properties sheet, specify the
filename, file folder, date and version properties of the target file you
want to check in the target machine. Please also customize the 'Property'
name of that File search item, for example CHECKDLL1. (CHECKDLL2,
CHECKDLL3, CHECKOCX...)

3. Open the Properties sheet of the corresponding files in your setup
project (Right click the target file node in the Solution explorer, the
press ALT+Enter), specify the following in its 'Condition' field:
NOT CHECKDLL1


I hope the above information helps, if you have any questions or concerns,
please do not hesitate to let me know. I am standing by to help you.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi Gary,
1. Add a File Search item, click main menu View | Editors | Launch
Conditions, then select 'Add File Search' on the 'Search Target Machine'
node.
Click to expand...

It was only after I posted my original question that I discovered the
Windows Installer File Versoning rules at the following page in the MSDN
Library:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/file_versioning_rules.asp

Can I just let the default rules take care of whether a file gets
overwritten, or do I still need to create a 'Search Target Machine' Launch
Condition for each DLL and OCX file?

Thanks,
Don
 
Hi Don,
Can I just let the default rules take care of whether a file gets
overwritten, ...
Click to expand...

No Problem, just can let the default file versioning rules works for you.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top