I'm no expert wrt to symbols so treat this advice as an old drunk sailor sitting at the bar telling a story..... :-)
I did a google search and a lot of people seem to not like _NT_SYMBOL_PATH. There seems to be some good things to be said about Symbol Server. Can I assume that your installer is some sort of SDK? Or are you perhaps automating an internal process? Any advice given would depend on the answer to that question (e.g. does the end user want to contol his own destiny or is it a captive audience ). However, I'm not going to go there anyways because I'm just an old drunk old sailor today. (PS- No offense meant for any squids that might be out there. Oorah ) --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me ----- Original Message ---- From: Mark Modrall <mmodr...@mzinga.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Thu, February 10, 2011 7:39:08 AM Subject: Re: [WiX-users] Wix and "tricky" environment variables Hi Chris... Thanks for the tip on App Path; I didn't know about that one. Unfortunately, I used PATH as an example because I thought that's the one people would be most familiar with, but there are a number of environment variables that function similarly. My own fault for not being more direct. What I'm actually trying to maintain is _NT_SYMBOL_PATH. I'm trying to add the directory where my .pdbs live so that my GAC'ed components can still get symbol info in stack traces. _NT_SYMBOL_PATH works similarly to PATH in terms of syntax and function and Wix would act on them pretty much the same way. Mark -----Original Message----- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Thursday, February 10, 2011 6:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix and "tricky" environment variables I'll be honest, it's 2011 and I'm hard pressed to understand why software applications still cling to the need to be in the "PATH"... a concept that originated some 30 years earlier. Can you redesign your application to not need to be in the path? Or, can you use AppPaths to make certain executables and http://www.sepago.de/d/helge/2010/08/26/how-the-app-paths-registry-key-makes-windows-both-faster-and-safer Otherwise, I'd suggest that if the built in Env@Part First|Last isn't working that you could change it to All and then use a custom action to do your own parsing ( dedupication, sorting, appending and so on. ) I'd test it really good though because I've never done this and I'm not sure what the gotchas would be. --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me ----- Original Message ---- From: Mark Modrall <mmodr...@mzinga.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Wed, February 9, 2011 2:58:40 PM Subject: [WiX-users] Wix and "tricky" environment variables Hi... I'm looking to get my installer to appropriately set an entry in one of those "tricky" environment variables, like %PATH%. By "tricky" I mean shared and accretive - it's a multi-value crossroads that everybody and their brother will be mucking with. I want to make sure our addition gets in there but don't want to just keep appending our root every time the installer is run. In the same vein, I can't just blank the variable when our product is uninstalled. So I was thinking I'd add a custom action type 51 to get the value into a property and a conditionalized component with a test on the value, but I'm not quite clear on how all the pieces would fit together... Something like <Component Id="SetPath"> <Condition><![CDATA[NOT EnvPath><C:\Program Files\Mypath;]]></Condition> <Environment Id="EnvSetPath" Action="set" Name="PATH" Part="first" Permanent="yes" System="yes" Value="C:\Program Files\MyPath" /> </Component> ... <CustomAction Id="EnvPath" Property="EnvPath" Value="[%PATH]" /> Problem is that all the examples I'm cribbing from are using ellipsis too, so I'm not sure if I have to declare what phase the custom action will be executed in, etc. Am I on the right track? Thanks Mark ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
