Installed the 3.6 beta (3.6.2221.0) and they compile again
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Visual-Studio-WiX-project-3-6-beta-installed-3-6-RC0-error-compiling-tp7455597p7455915.html
Sent from the wix-users mailing list archive at Nab
Hi,
We have some WiX projects that don't compile after installing 3.6 RC0.
Worked with 3.6.2120.0
The error:
Error 2 Method not found:
'Microsoft.Tools.WindowsInstallerXml.WixErrorEventArgs
Microsoft.Tools.WindowsInstallerXml.WixErrors.InvalidPlatformParameter(System.String)'.
candle.exe
Some more info: Visual Studio 2008 and Windows 7 x64
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Visual-Studio-WiX-project-3-6-beta-installed-3-6-RC0-error-compiling-tp7455597p7455607.html
Sent from the wix-users mailing list archive at Nabble.co
Thanks for mentioning those hotfixes.
In the end I've included them in the bootstrapper. It seems to be the right
way compared to increasing the file version of the assemblies.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingProducts
I've done some more tests and it seems that on Windows Installer 4.5 the
assembly is removed from GAC after a major upgrade.
Good to see that at least on 5.0 got fixed.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExistingProducts-after-the
Hi,
There is http://support.microsoft.com/kb/905238 a knowledge base article
(mentioned also on the WiX Documentation) that describes the case of an
assembly from GAC missing after a major upgrade. One of the solutions was to
schedule *RemoveExistingProducts *action to occur after the *InstallF
Thanks for the response.
Sorry, I haven't mention. I use DTF and
Microsoft.Deployment.WindowsInstaller.MessageResult.Retry .
Unfortunately, I was not using the buttons argument from the callback method
that specifies what buttons can be displayed. Just noticed that for
RMFileInUse there is jus
Hi,
I have a small setup that uses Embedded UI.
During uninstall the RMFilesInUse (I just start an executable that was
installed) message type gets to the embedded UI and I return
DialogResult.Retry . I would expect the unistall to try again and check if
the file is still in use. If it is still
If anyone is getting the "EXEC : error : No CA or UI entry points found in
module" message, make sure that the class implementing IEmbeddedUI is
public.
haripanicker wrote:
>
>
> I created a custom action project that implements the IEmbeddedUI
> interface.
>
> when i compile it.. i get thi
n at time(s)
> during the transaction but there sometimes seems to be a window of time
> where the cancel will be ignored before the disable request arrives.
>
> See INSTALLMESSAGE_COMMONDATA in the
> http://msdn.microsoft.com/en-us/library/aa370573(VS.85).aspx page.
>
> -O
Hi,
I'm using the Embedded UI feature (thanks DTF) from Windows Installer 4.5
and noticed that the installation is not always canceled when returning
MessageResult.Cancel from the: public MessageResult
ProcessMessage(InstallMessage messageType, Record messageRecord,
MessageBoxButtons buttons, Mes
Hi,
I'm building an embedded UI with DTF and noticed that sometimes the Shutdown
method is not called in the uninstall phase. When this happens, an
InstallMessage.Terminate is received in the ProcessMessage method. Is there
anything I'm missing ?
I have a feeling that this is more a question
12 matches
Mail list logo