You only have to execute the tools\OneTimeWixBuildInitialization.proj
elevated once. This was true in the old builds too, it was just hard to
find the targets you needed to run once elevated. That's why I pulled it
out. <smile/>
I've always built the WiX toolset from an unelevated cmd prompt. Always.
On Mon, Feb 18, 2013 at 10:09 AM, Hoover, Jacob
<jacob.hoo...@greenheck.com>wrote:
> One other thing I’d like to mention, prior to 3.7 I know the old build
> process was assuming you were running as admin. I prefer my Wix builds to
> be isolated from the Wix RTM (I have both on my machine). It would be nice
> if any of the build tasks that modify system state would require a
> property/parameter to be passed to the build system to activate them.
> Maybe this would allow for less fear of building the whole toolset just to
> support extension fixes/enhancements/additions?****
>
> ** **
>
> **
>
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
