I for one have never understood or really dug into why it would even matter. .NET is supposed to be XCopy deployment so if I deploy a .NET assembly privately, why would or should MSI even care that it happens to be a CLR assembly? That said, I always select "Properties Only" in InstallShield so that that the MsiAssembly table like a good little drone.
I would profile your application to understand why it's not running. Get a stack trace, open the EXE with REflector/ILDasm, use filemon, regmon, whatever to get an understanding of why the program isn't working. Heck, maybe you just don't have .NET installed because your using WiX and you probably don't have a bootstrapper. But I'm guessing that your in the weeds right now in trying to figure out what's "wrong" with the installer. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Tue, 11/17/09, JKLists <jkli...@ifm-services.com> wrote: > From: JKLists <jkli...@ifm-services.com> > Subject: Re: [WiX-users] Private Assemblies? > To: "General discussion for Windows Installer XML toolset." > <wix-users@lists.sourceforge.net> > Date: Tuesday, November 17, 2009, 9:39 AM > > > Just a guess, but in seeing that the registry entry is > in the Installer > > area, I am wondering if in the IS install if these > private assembly files > > are marked as the KeyPath, which is why they are being > recorded here? > > > > I couldn't say. The WiX version has them marked as keypath > also.I'll do > what Bob recommended and try decompiling the MSI files to > look for clues. > > This MSDN article > <http://msdn.microsoft.com/en-us/library/aa367758%28VS.85%29.aspx> > > mentions that region of the registry for private assembles, > which has > lead me to where I'm at now. :) That article, however, > states: > > If a Windows Installer package installs or > advertises assemblies, > the installer stores information about those > assemblies in the local > system registry. Please note that these > registry keys are only > intended to be used internally by Windows > Installer and they should > not be relied upon by your application. The > content, location, and > structure of information stored in these keys > is subject to change. > Applications should rely upon > *MsiProvideAssembly* > <http://msdn.microsoft.com/en-us/library/aa370355%28VS.85%29.aspx> > to manage assemblies. > > > So I'm hesitant to just copy the registry keys. It implies > that > something else is missing. > > > As far as the crashing is concerned, have you > confirmed if your private > > assembly files were actually installed? > > Yes. I've installed both side by side, diffed both > directories and files > using BeyondCompare <http://scootersoftware.com/>, copied them over each > > other. I'm fairly confident that the problem isn't the > existence of > files and/or directories. > > As another developer said, "It shouldn't be this > interesting." *grin* > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal > Reports 2008 30-Day > trial. Simplify your report design, integration and > deployment - and focus on > what you do best, core application coding. Discover what's > new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
