App isolation doesn't really require the MsiAssembly* table values for managed assemblies (it does for native), but the additional benefit in WiX is that you can access bind variables for that assembly as documented in wix.chm.
fgc wrote: > Hi all, > > So far I know that setting the Assembly=".net" attribute installs my > assembly into the Global Assembly Cache. But why should I specify > AssemblyApplication in addition to Assembly=".net"? My understanding is that > if I specify both attributes I end up with an installer that contains an > MsiAssembly / MsiAssemblyName table and installs the assemblies into my > installation directory structure, not into the GAC. Therefore the > information in these two tables is not really required. > Is there any special use case where it is recommended to do this? So far I > treat all assemblies that are not installed into the GAC like any other > file. Does it ever make sense to treat .NET assemblies different if they are > not installed into the GAC? > > Thanks! > > -- Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
