On Thu, Nov 19, 2009 at 11:00 PM, Chad Petersen <chad.peter...@harlandfs.com> wrote: > Aren't shell extensions either a DLL or OCX file as the entry point? > Think about what you have to do to manually deploy your shell extensions > and write down the steps (if it helps). These are the steps that you > would then author in WiX to automate the process through an MSI. A > simple outline with things that are common > > 1. Confirm it is a Windows OS > 2. Confirm it is one of the version(s) of Windows you support > 3. Detect where Windows is installed if needed > 4. Copy extension to proposed folder (your own, or perhaps System32) > 5. Register the extension with the system > 6. Restart Windows if needed
Hello Chad, Aye, shell extensions are all DLLs. I believe I know the requirements of my shell extensions, but I am unsure as to the best installing habits. For example, you recommend system32, but I recall reading that starting with Vista I believe it was, Microsoft is advising against installing stuff into System32. I have no real need for backwards compatibility (thankfully), so I focusing fully on Windows 7 compatibility and guidelines in this matter. But to me, this also means I should be getting it mostly right at my first try, rather than mostly wrong. :) Regards, Jan Wester ------------------------------------------------------------------------------ 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
