Yeah, VS and MSBuild and Votive conspire in evil ways to prevent the value
from coming back in a way that you can edit. You can actually get into this
same situation with C# projects.
You have to edit the .wixproj (or .csproj is you mess up your C# project,
like I did once) to fix it.
On Tue, Jun 21, 2011 at 1:21 PM, Eric Teutsch er...@powersoft.ca wrote:
I've got an undefined preprocessor variable in my .wxs file, but when I
entered it into the Define preprocessor variables: edit box as
var.Variable=abc it made no difference. I then tried the probably really
wrong way of
$(var.Variable)=abc
At this stage the Votive editor wouldn't let me undo this change. Anything
I tried produced the error message:
The expression .Variable cannot be evaluated. Method
'System.String.Variable' not found
All I could do is close the project without saving it.
PS: Figured out now that I'm supposed to declare it as simply
Variable=abc
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
virtually, Rob Mensching - http://RobMensching.com LLC
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
