Is there any way to create a clickonce deployment where certain assemblies or files in the manifest can be designated as not needing to be downloaded unless the user performs some action in the application that requires them?
Currently, we have a fairly monolithic ClickOnce application and are researching ways to refactor it into separate assemblies.
I am trying to find a way to reduce the initial payload size when I publish an update and only download assemblies when they are required by the user. Is this possible within the ClickOnce architecture? Is there an alternative?
Thanks, -MrB