Redefining the package cache locations is definitely a good feature for Burn.
Would you mind starting a WIP to capture the design? There are a lot of
tradeoffs to discuss.
See: http://wixtoolset.org/development/wips/0000-wix-improvement-proposal/
From: Heath Stewart [mailto:hea...@outlook.com]
Sent: Friday, January 10, 2014 11:31 AM
To: wix-devs@lists.sourceforge.net
Subject: [WiX-devs] RFC: Using KnownFolders/CSIDLs for package cache
I've gotten a lot of feedback on my blog and through other sources about Burn's
package cache re: Visual Studio. It's big, but it's there for good reason
(mainly, because prompt for source issues were much, MUCH higher in volume than
size complaints). I'm writing a new post on how to work around this (originally
was intended for MSI itself but that team forbade it ;).
So I was curious what people's thoughts were on defining both per-user and
per-machine KnownFolders/CSIDLs (if KnownFolders aren't supported on all
desired platforms) for the burn package cache. To support current bundles out
there, they could fallback to AppData if the cached payload isn't found.
This would allow power users and domain admins to use existing infrastructure
to decide where the package cache should be created, since it seems many
devs/users are using a combined SSD/HDD solution where the HDD has the monster
capacity and the SSD is mainly for Windows itself.
Heath Stewart
Software Design Engineer
Visual Studio, Microsoft
http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
