We've got a WiX 2.0 based install, and have an upgrade scenario that I'm not
sure how to accomplish. For the new version of the product, the default
(configurable) install directory has changed. When upgrading existing
systems, we need to copy some XML configuration info from the original
install
Done.On 8/25/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
Kevin Dente wrote:> Can't use gacutil - it doesn't get installed with the .NET Framework> 2.0 runtime, only with the SDK.>> We'll probably just go with the hack-ish solution for now - do a> FileSearch in the
Our Wix-created MSI creates IIS virtual dirs and registers .NET 2.0 as the handler for those web apps. Generally, it works great. However, there's an obscure error condition where if the user has installed IIS after the 2.0
runtime was installed, ASP.NET is not registered correctly in IIS, and the
Can't use gacutil - it doesn't get installed with the .NET Framework 2.0 runtime, only with the SDK. We'll probably just go with the hack-ish solution for now - do a FileSearch in the c:\windows\assembly directory.
On 8/25/06, Joe Kaplan <[EMAIL PROTECTED]> wrote:
This sounds like a slightly hard
r that right now.
Thanks,KevinOn 8/24/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
Kevin Dente wrote:> Is there a recommended way to verify that a specific component is> installed in the GAC as a pre-requisite for an install? All I'm seeing> right now is a FileSearch, and that seem
Is there a recommended way to verify that a specific component is installed in the GAC as a pre-requisite for an install? All I'm seeing right now is a FileSearch, and that seems a little hack-ish (since the structure of the GAC is supposedly opaque).
Thanks,Kevin
-
6 matches
Mail list logo