Yup, this is for an excel addin.
it's a 32 bit app. On a 64 bit PC it installs in the x86 folder.
I got a workaround for the solution. The ExitDialog on button click, I called a
custom action to modify the EXCELPATH and immediately after that the excel is
launched post install.
-Original
Hi
I have a installer created which gets installed successfully on Dev
Environments ,but when installed on UAT and Test environments the installer
rolls back what ever it has installed. Not sure what could be issue be
with.If it is related to IIS .Please provide me sample code snippet how the
rel
This problem is solved now. For the record, I used Nick's CopyResource idea
and it worked. For anyone else who tries this solution, there are two
additional things worth pointing out:
1) Copying a resource in this way can leave it behind on the target computer
in the temporary installation folder
The question is where in the registry is it reading it from... the 32 or 64 bit
hive. On my machine, the 32 bit hive has the 32 bit path and the 64 bit hive
has the same 32 bit path. This makes sense to me as I have a 32 bit version of
office installed. I don't think this is Wix specific, as I'm
No one ever replied to this, however I was able to find the answer on my own.
For anyone else who runs into this problem, here is the answer:
If your managed bootstrapper application is complied for .Net 4.5, your
BootstrapperCore.config needs to state the following:
-Origin
Has anyone been able to create the MDF and LDF paths when specifying a path via
command line?
I've tried adding the method but it will not create the folder.
However, if the folder path exists it works. I would like the end user to
Does the verbose log file say the Component is being removed?
On Thu, Apr 25, 2013 at 7:53 AM, David Steadman wrote:
> All
>
> I been trying to have registry key unistalled from a system, the keys
> get created but on install they still remain ,
>
> I have tried the following after the syntax
All
I been trying to have registry key unistalled from a system, the keys
get created but on install they still remain ,
I have tried the following after the syntax but nothing is working..
am I doing something wrong,
ForceDeleteOnUninstall="yes" Action="createAndRemoveOnUninstall"
I even tri
Ah, I was still using a pre-change build.. doh
It does work, however the log reports that after the reboot, InstallFolder
is (re-)initialized to the default value, but the correct value is shown in
the pararmeters passed through on the MSI command line (and the Variable
dump).
Slightly logging bu
It's not a bug in the WiX toolset. It's a behavior of the Windows Installer
(aka: MSI). You should ask them why they made that decision. It frustrates
developers all the time.
On Wed, Apr 24, 2013 at 11:33 PM, Shashank Padmanabhan (Aditi Technologies
Private LTD) wrote:
> Isn't this a bug in WI
Classification: Public
Check the NTProductType - numeric product type from OS version information.
private const int VER_NT_WORKSTATION = 1; private const int
VER_NT_DOMAIN_CONTROLLER = 2; private const int VER_NT_SERVER = 3; private
const int VER_SUITE_SMALLBUSINESS = 1; private const int VER_SU
Using the:
http://msdn.microsoft.com/en-US/library/aa370556.aspx
.NET 4.5 can run on:
Windows 7 (v6.1 and SP1) and also Windows Server 2008 R2 (v6.1 without any
SP).
This condition matches Windows 7: (VersionNT = v6.1 AND ServicePackLevel >=
1)
But how to match the Windows Server 2008 R2, as it h
I ask the same thing, any examples of the: "Bundle/@Condition attribute"
//Sam
On Wed, Apr 24, 2013 at 3:41 PM, Nick Miller wrote:
> Is there anywhere where I can see an example of this? I tried using the
> same condition I have for .Net 4.5 and it still skips the prereq and tries
> to run the
13 matches
Mail list logo
