So the first question is about the download dialog for the reference configuration. Something needs to display errors and show progress when it takes time to download the configuration. Lets assume an error can appear outside the dialog - maybe this needs
an option not to display the download dialog for reference configurations? Thoughts?
I agree, I think it should be an option... if an error occurs, it will be displayed in a modal I guess..?
I thought about merging this download process into the main window, but this presents several problems. The most obvious one is that you need the reference configuration already downloaded to display the dialog with proper text, locale and options. If I
merged them, the flashing would be the same except now you have the main dialog flashing in English, then switching to Spanish for example.
I agree... the merge wouldn't work.
I made a commit that fixes the download / cancel @ rev. 55043 and the fix for the order of components @ rev. 55052 (it's not as easy as the loop, that one's correct - the components are inserted on a different (UI) thread so the insertion is queued - the
index at which to insert was calculated before the actual insertion occurred, being zero most of the time) - the fix is to move this to the UI thread.
I'd gladly take a new revision if the new reference config dialog is an option... (I see the thread issue now..)
To display download size of a component as part of a description something would need to figure out the download size. How do you see this happen? Do file a feature request if you can tell a good story :)
My dev mgr looked at my POC and it was the first thing he said... "As a user, I'd lile to know how big each MSI is before I click Start..." - We pre-req .NET Framework 4.0 and VS Shell 2010.
Unsurprisingly, GetFileAttributesExW() doesn't like http.. So far, I've added another <Component> element called sourcesize which is added to the component description (works but obviously not dynamic).
p.s. I've upgraded the sln/proj's to VS 2008 (works okay) but VS 2010 moans about various things...
p.p.s. you seen WiX's Burn? sadly, not a patch on this... ;)