"Scott McQuown" <smcquown@spamsucksmidsouth.rr.com> wrote in message
news:eODcAo$uDHA.2880@tk2msftngp13.phx.gbl...
> I get this error when I try to build the setup/deployment project for my
> application. Cannot find any info on what this HRESULT means (different
from
> the one mentioned in post dated 11/6 and I have never had InstallShield
> developer installed).
>
> Any help would be appreciated.
>
>

"Scott McQuown" <smcquown@spamsucksmidsouth.rr.com> wrote in message
news:eODcAo$uDHA.2880@tk2msftngp13.phx.gbl...
> I get this error when I try to build the setup/deployment project for my
> application. Cannot find any info on what this HRESULT means (different from
> the one mentioned in post dated 11/6 and I have never had InstallShield
> developer installed).
>
> Any help would be appreciated.
>
>

"Phil Wilson" <phil.wilson@unisys.spamcom> wrote in message
news:%23u2mynbvDHA.1888@TK2MSFTNGP10.phx.gbl...
> IIRC, I've seen this happen when mergemod.dll is no longer registered.
Find the
> mergemod.dll associated with Visual Studio (probably in Common
Files\Microsoft
> Shared\MSI Tools) and register it with regsvr32. This DLL is shared
between
> Visual Studio, InstallShield, the Platform SDK, and sometimes uninstalling
one
> of these de-registers it (which means they ain't sharing it right).
> --
> Phil Wilson [MVP Windows Installer]
> ----

"Scott McQuown" <smcquown@spamsucksmidsouth.rr.com> wrote in message
news:u1%23fWpevDHA.2440@TK2MSFTNGP12.phx.gbl...
> Thanks for the reply. I tried your suggestion w/mergmod.dll, but am still
> getting the same message. There are two build errors with the same result,
> so I suspect there could be two items that need re-registering. I'll keep
> digging.
>
> Scott
>
> "Phil Wilson" <phil.wilson@unisys.spamcom> wrote in message
> news:%23u2mynbvDHA.1888@TK2MSFTNGP10.phx.gbl...
> > IIRC, I've seen this happen when mergemod.dll is no longer registered.
> Find the
> > mergemod.dll associated with Visual Studio (probably in Common
> Files\Microsoft
> > Shared\MSI Tools) and register it with regsvr32. This DLL is shared
> between
> > Visual Studio, InstallShield, the Platform SDK, and sometimes uninstalling
> one
> > of these de-registers it (which means they ain't sharing it right).
> > --
> > Phil Wilson [MVP Windows Installer]
> > ----
>
>
>

"Phil Wilson" <phil.wilson@unisys.spamcom> wrote in message
news:eEBlCMovDHA.3536@tk2msftngp13.phx.gbl...
> It's possible a Repair of Visual Studio would fix it, but it will most
likely
> take a couple of hours.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Scott McQuown" <smcquown@spamsucksmidsouth.rr.com> wrote in message
> news:u1%23fWpevDHA.2440@TK2MSFTNGP12.phx.gbl...
> > Thanks for the reply. I tried your suggestion w/mergmod.dll, but am
still
> > getting the same message. There are two build errors with the same
result,
> > so I suspect there could be two items that need re-registering. I'll
keep
> > digging.
> >
> > Scott
> >
> > "Phil Wilson" <phil.wilson@unisys.spamcom> wrote in message
> > news:%23u2mynbvDHA.1888@TK2MSFTNGP10.phx.gbl...
> > > IIRC, I've seen this happen when mergemod.dll is no longer registered.
> > Find the
> > > mergemod.dll associated with Visual Studio (probably in Common
> > Files\Microsoft
> > > Shared\MSI Tools) and register it with regsvr32. This DLL is shared
> > between
> > > Visual Studio, InstallShield, the Platform SDK, and sometimes
uninstalling
> > one
> > > of these de-registers it (which means they ain't sharing it right).
> > > --
> > > Phil Wilson [MVP Windows Installer]
> > > ----
> >
> >
> >
>
>