OK here's a real WTF, I use wise script today to split out a path, then I wanted to write to the Windows Installer property [NEWPATH]. Everything is OK, I get the WS variable %NEWPATH% to populate but when I set Windows Installer property [NEWPATH], bollocks as the English say. Fuck all. Blank. Some jerk said you needed to have the empty Windows Installer property first. Fucking bulllshit, excuse my french, Wise script says not.

WTF? Here are some of the things I tried:

with and without the []
calling the wise script CA different places in the InstallExecute sequence.
I thought this would be the easy part after struggling with the parse in wise script. AFter getting that right, the Windows Installer property simply would not populte at all.

And of course Wise has absolutely NO goddam samples of how to use this. I am upset and feeling really stupid. Somebody tell me this is a problem with wise script, or give me a good sample that works.
Should have just used friggin VB script....sigh!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Should have just used friggin VB scriptI honestly don't know why anyone would use WS over VBS. I toyed with it for all of 20 minutes when first starting out with Wise and that was enough.
Answered 03/20/2010 by: VBScab
Red Belt

Please log in to comment
0
works for me:
The Get Windows installer Property action contains property name without square brackets
The Set Windows installer Property action Property name without square brackets (doesn't matter if this exists in the msi or not) Then the property Value will be you wisescript property surrounded by % signs

item: Custom Script Item
Filename=Get Windows Installer Property.wse
Variable Name1=_PROPERTYNAME_
Variable Value1=BE_PROJECT_SERVER
Variable Name2=_PROP_VAR_
Variable Value2=TEST
Variable Name3=HELPFILE
Variable Value3=Wise Package Studio\WiseScript Editor\wise32.HLP
end
item: Custom Script Item
Filename=Set Windows Installer Property.wse
Variable Name1=_PROPERTYNAME_
Variable Value1=NEW_PROP
Variable Name2=HELPFILE
Variable Value2=Wise Package Studio\WiseScript Editor\wise32.HLP
Variable Name3=_PROPERTYVAL_
Variable Value3=%TEST%_EXTRA
end

Answered 03/22/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
agree with Ian except in this case you could do it all native with an appsearch lookup for the var in question.
Answered 03/22/2010 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
it's pretty easy to use parse (compared to VBscript, although I probably could have found/adapted a find/replace text script without a lot of effort). but add that to the effort of debugging, I was seriously feeling kind of stupid. it was one of those really stupid, irritating days when nothing seems to go right. Thanks for the feedback to you all anyway, next time hopefully things will go smoother.
Answered 03/22/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
great avatar BTW, just noticed it! LOL...
Answered 03/22/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
After all this time, Owen, you only just noticed?!?
Answered 03/22/2010 by: VBScab
Red Belt

Please log in to comment
0
Ya I'm a bit clueless. also saw you over on the symantec/wise boards i went browsing the other day. man you do keep busy! take care!
O
Answered 04/09/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity