Circular dependencies with Dynamic Suite Composition and App-V 4.5

App-V 4.5: Circular dependencies with Dynamic Suite Composition

App-V 4.5: Circular dependencies with Dynamic Suite Composition — Tue, 23 Jun 2009 13:26:07 GMT

PingBack from http://www.ditii.com/2009/06/23/app-v-4-5-circular-dependencies-with-dynamic-suite-composition/

re: Circular dependencies with Dynamic Suite Composition and App-V 4.5

ksaunam — Tue, 23 Jun 2009 13:38:59 GMT

"So if you decide to make A depend on B, you sequence B first, but use the sequencing wizard to remove any shortcuts or file types it creates."

Actually, if you publish these packages traditionally you still have to publish at least one OSD for dependency package as well as Management Server checks permissions based on published apps.. unless that has changed in CU1 or later?

Of course, that OSD does not need to create actual shortcuts or anything but it must be published and/or assigned to user launching the primary package.

br,

Kalle

re: Circular dependencies with Dynamic Suite Composition and App-V 4.5

peelman — Tue, 23 Jun 2009 16:12:57 GMT

While not really a circular dependency, I had to do a similar OSD setup for FactoryCAD 12, which needed to be suited with AutoCAD 2009. Since FactoryCAD is more of a set of profiles and templates, and less of a stand alone program, no OSDs are created at sequence time. So, I had to duplicate one of AutoCAD's OSDs, drop it into the FactoryCAD project directory, and do a bunch of tweaking to get the GUIDs happy and get AutoCAD to launch with a specific profile. It was an interesting deployment, but for all its complexities, it was still pretty straightforward when compared to some of the fiasco's we have had to deal with (IronCAD 11, AspenOne 2006, Visual Studio 2008, etc).

re: Circular dependencies with Dynamic Suite Composition and App-V 4.5

tguinn — Thu, 02 Jul 2009 09:07:42 GMT

You can delete the shortcuts in the sequencing wizard without deleting the OSDs. Expand the individual entries in the left pane and click on shorcuts. Then delete each shortcut as well as each file type from the adjacent OU. This will simply remove the shortcut location placement information without deleting the OSDs and still allow importation and provisioning in th App-V MMC.