Did you confirm that you’re using the shared framework? That should keep the app size down. The main reason for the app size is that all the bits of the framework that your app relies on are being compiled into the package (x3 if you’re supporting all three architectures). The point of the shared framework is to try to again abstract this so that every app doesn’t need to install it.
Nick Randolph | Built to Roam Pty Ltd | Microsoft MVP – Windows Platform Development | +61 412 413 425 | @thenickrandolph | skype:nick_randolph The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built to Roam Pty Ltd does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built to Roam Pty Ltd. From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Thursday, 7 July 2016 6:41 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: Re: UWP build and packaging Been doing it for a while now and yes build process is ridiculously long. Better with Update 3 and particularly if you can leverage the shared framework (https://blogs.msdn.microsoft.com/dotnet/2015/09/28/whats-new-for-net-and-uwp-in-win10-tools-1-1/ ) Good to hear from you, I was getting worried that no one was doing this. I have VS2015 SP3 installed, so I'm not sure if a 5 to 15 minute build is expected or not. I can live with this as I don't deploy often. What is still a serious problem is the size of the package. I tried all sorts of tricks to get the size down, but with little effect. A colleague reported that my 65MB package installed and was reported as being 4MB on disk. I can't believe this is normal and I'm hoping there is some stupid fix that I've missed. Greg
