Video Screencast Help

Commas in File Version for Import Software

Created: 21 Jun 2012 • Updated: 22 Jun 2012 | 1 comment
This issue has been solved. See solution.

I'm running all the latest SMP 7.1 SP2 components along with the v4 rollup.  When I go to "Import Software" and point it to "install_flash_player_32bit.exe" (http://download.macromedia.com/pub/flashplayer/support/acrobat/install_flash_player_32bit.exe), Software Management Solution imports the file version although instead of "11.2.202.235" it fills in "11,2,202,235" (i.e. it replaces the periods with commas).

I believe the first Properties tab of the Software Resource is just informational but is this normal behavior for an exe import and, more importantly, will this be a problem if I set a file version detection rule?  I'm hoping this period to comma change is just visual for the import and when the detection rule actually fires off, it'll use periods in the file version as specified in the detection rule's properties.

Comments 1 CommentJump to latest comment

Juri Tsjornoi's picture

Hi!

First of all let me explain why commas appear in the File Version field when importing "install_flash_player_32bit.exe" package. When importing new software resource having EXE extension file version is actually taken from file properties of the package that is being imported. In our case the file version for "install_flash_player_32bit.exe" package is 11,2,202,235 (you can right click on the installation package, open Properties, on the Version tab select File Version list item,and the value for the File Version will be 11,2,202,235).

What about detection rules based on file version, File Version detection rule correctly detects installed software even if a file version in the rule is specified with commas instead of dots.

SOLUTION