Base Application Multiple Deployment Types Per Application

I understand that it's sometimes a need to install x86 applications on x64 based systems like when you have required plug-in(s)/add-on(s)/extension(s) that only run on the x86 version of the application. It would be optimal to have a right-click options like "Combine multiple architectures into a single application" so you can choose to combine when appropriate. Combined applications can save resources and time by automatically installing the appropriate architecture when configured to do so. When you have one applications per architecture you potentially need to create multiple (deployment) collections targeting architecture, those collections require evaluation. You end up with more collections, more applications, more deployments all of this takes time to create and uses resources over time to maintain.

I agree, it's not something that is applicable to all applications. However there are certain applications that would benefit from it as they just don't work on a different architecture. Not a big deal, this new feature is already saving us a lot of packaging time so I can't complain.

Hey Pierrre,

Good feedback, we have thought about this in our design, but it's challenging because some 32-bit apps are often installed on 64-bit OS's (Notepad++, Java, Etc.). The best workaround we thought of is to create different applications per architecture, and you can control how to deploy those applications.