Hi,
while presets cover to some extent - set to ESD and ISO destination for mastering and save, set to no saving or WIM compression when editing, I do understand that a mode switch would be more flexible across images.
Regarding a WIM being read-only, that fits into the next task of ISO handling. I rather you can right-click on a WIM and decide "Revert to source", than not to save the WIM. The WIM being loaded is always the one being edited and saved to (that's how Mounting works), but how do we handle the initial load and prompting for the temporary directory is being planned.
Let me point to the Source - Tools, all of these are just mods of operation reusing the tool's capabilities and automating certain tasks.
I was planning next for the Component removal, a mode switch, the 'no Windows Update' (removes much more), and 'keep Windows Update compatibility' (removes less in WinSxS and limits certain removals) modes.
Now that you mentioned an image handling mode, it is starting to get interesting and why I'm writing this much while thinking about it...
Interestingly the fast WIM handling mode/lockdown is already used in the Host Refresh tool. It locks certain operations to speed up getting to that update WIM, preventing the user to slow the process down more than necessary.
The only complaint I have about the image handling mode is the unnecessary decision complexity.
I mean it's so simple to switch to a WIM or not save image after processing, that I am struggling to see the need for locking it any further.
Those Apply - Image tasks - Saving mode switches are there for that reason, to choose if you want the image unmounted, saved, etc.
With the new info about the upcoming read-only ISO feature, WIM reversion, master preset handling, do you still need something in that workflow with the image modes idea?
Thanks!