Hi,
I would like to know if I can use WIX to create installations for Windows
Mobile Phone? If so where can I find resources for this subject?
--
Best regards,
Itzik Kasovitch
--
Hi,
I'm trying to create installer which can be installed using both GUI or
commandline installation.
When I have tried I was able to do either by only GUI or by only
Commandline. :(
Can anyone suggest how to do it by both the options.
Regards,
Vijay Chander
-
I will follow up on this when I get to the office tomorrow. I pinged the VSTO
team for guidance and I haven't heard back from them yet. I believe the answer
is that the VSTO installer component that ships with VSTO runtime only performs
per user installs. I'm trying to confirm this. Anyone wishi
I'd like to do something like this
I have pre-existing code to do what I need in a CA, but I'd love to make
things more declarative.
-john
On Mon, May 31, 2010 at 2:35 PM, Neil Sleightholm wrote:
> Could y
Thank you for your suggestion.
We wanted to minimize installation download size so we limited installed
language packages to the same languages as the programs are installed
in. Sadly this brought us this problem :(
We are currently supporting 12 languages and each language is updated
independe
Hi All,
Does anybody have info about such issue. With build 3.5.1728
I'm still getting error (part of log is below) during upgrade application
hosted on IIS7. There are no errors on IIS 5 or IIS6.
Is IIS7 the reason of errors or maybe there are some mistakes in my code?
===
Hello everyone,
new releases of my app are always installed with a major update and the old
version of the app is always uninstalled if the MSI for the new version
runs, just before the MSI of the new version does its work copying files,
creating registry entries and so on. Now if my app currentl
Hi there,
just for anybode who is interested in this issue:
Thanks dG for your suggestion, but I didn´t want to put so much effort
in it.
Therefore I just added a line on the bottom in a section called "dummy"
wiht the normal wix tool kit.
It seems that most ini-parsers are takting the last line
Hi,
Are u using following commands
1. candle.exe
2. Light.exe -ext WixUIExtension (without use of localization)
I think this may give you a pointer.
Regards,
Swapnil Sankla | Software Engineer | Persistent Systems Limited
swapnil_san...@persistent.co.in | Cell: +91 9960851096
Persistent Syst
Your application would have hold a "lock" on those PNG files that denies
"Delete" (via sharing mode) using its file handle until the application is
shutdown.
-Original Message-
From: Stefan Kuhr [mailto:kustt...@gmx.li]
Sent: Tuesday, June 01, 2010 3:45 AM
To: wix-users@lists.sourceforge.
Okay! I have finally more closely identified the problem I'm having. In my
installer, I was attempting to get a settings file to REMAIN INTACT on a
major upgrade. I finally got this to work with the suggestion to set
This is successful in forcing this component to leave the origina
Hi,
Please find the excel error. This error occurs when I starts excel. If I
removed this hotfix excel opens properly. This is happening on clean
machine without any com addin. We have office 2007 sp2. It shows
excel.exe*32 in task manager.
These are the error details
Problem signature:
Pro
WebApplication is associated with its parent WebVirtualDir. My gut says that
you want the Data WebVirtualDir to be a child of the Panopto WebVirtualDir and
that both WebVirtualDirs should be running under the same WebApplication.
Hmm... I don't have a way to test this rig
Yes, sure, my application holds a lock on these files. I would expect that
MSI can deal with such a situation, because having a file open is an everday
scenario, even if this happens only for a short time. It can deal with exe
and dll files that are currently running and the files that are locked
Here is the response from the VSTO team. I'll see if I can make headway on the
crash, though my day today is solidly booked. It might be tomorrow that I have
progress on that front.
VSTO response ---
That's correct. The only way to install to all users is to use an MSI. All
ClickOnce
1 - Can you install MSI's on "Windows Mobile Phone"?
If yes then yes you can use WiX to create your installation packages. If
no then no. WiX isn't some magical tool with it's own installation
system, it simply creates Windows Installer packages.
2 - MSDN would be a good start.
Palbinder Sandhe
Removing
>From inside your UI element would be a good place to start.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Re
Not possible using standard Windows Installer UI. At best you can run a
CustomAction when the user clicks the Next button depending on which
option they have selected in the radio button & move your ComboBox to
the next Dialog page.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44
More information on what you're actually trying to do, where things are
going wrong & the code you're using to do it might get you further
towards answers.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, S
thank you. it worked.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/prroblem-with-short-cuts-tp5121815p5127247.html
Sent from the wix-users mailing list archive at Nabble.com.
--
I'm guessing this is a problem because the files are non-versioned. Try
using the CompanionFile attribute on those 2 files & link them to some
versioned files (DLL's, executables, etc) which will get replaced on
upgrades.
See -> http://wix.sourceforge.net/manual-wix3/wix_xsd_file.htm
Palbinder Sa
Try using "msiexec /i /l*vx " to get verbose logs.
I'm not sure on what info the WiX Standard Custom Actions like SqlExtension put
into the logs but those options should get everything & might help point out
where it's failing. For some reason I've got a feeling there is some Property
or vari
I have already tried this! I have been through several rounds of it, and the
problem is that if RemoveExistingProducts is set after InstallFinalize
(which makes the Settings.xml file remain intact), the CompanionFile does
work to show that the file is replaced, however, the Pathways.MDF file then
Not an IIS user myself but from what I've read IIS7 support is still in
mid-development for WiX 3.5 so you may be hitting a bug. Make sure
you're using the latest build of WiX 3.5 as bugs are fixed very
regularly.
Also your log extract is from the rollback, that's not where your error
is occurring
Personally I'd go with 3 but I already implemented something almost identical
for Shared data files rather than Shared libraries in our software 2 years ago.
If you want to block a user from uninstalling the MSI's manually & force them
to use your boostrapper simply add LaunchConditions with you
Ah so the old installer is the problem then not your new one. This will
be why people like Rob M. & Bob A say you should test upgrades before
you ship your first product (step 4 at
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm &
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/)
AH... okay, your response now finally makes some sense. Custom action is
what I was just looking at, as I don't have much of a notion of the
patching...
Just for the record, I DID NOT author the original installer for this
application, I am simply coming in after the fact with a new version.
Ok Thanks. I will wait for your reply.
Thanks,
Rahul
-Original Message-
From: Bryan Reich [mailto:bryan.re...@microsoft.com]
Sent: Tuesday, June 01, 2010 1:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VSTO excel Add in for all users
Here is t
Hi Blair,
I did some more investigation and reading archived posts to this group.
Until now I had RemoveExistingProducts scheduled before InstallInitialize in
all my installs. If I now schedule it after InstallFinalize, everything
seems to work. Is this the way to go? Is there any downside to sch
Hi all,
I am trying to modify TARGETDIR value at runtime in WIX using VBScript
Custom Action, but it seems that WIX doesn’t like Session.TargetPath. An
example is attached with this mail.*(Please rename Test.vb_ to Test.vbs)*
·*Test.vbs*: is the script containing Session.TargetPath call,
I define a desktop shortcut with following line
and have defined the icon reference as
When I install the application and take a look at the symbol path in the
created shortcut, I see a strange entry like
%SystemRoot%\Installer\{8AF15DBB-442D-4BBC-A1EF-77B70AD64065}\myexe.exe
I can't seem t
I am now working on getting the custom action going to back up the existing
settings.xml file. I am using this page as a guide:
http://blogs.msdn.com/b/jasongin/archive/2008/05/23/custom-action-project-templates.aspx
I have created a custom action project, and it builds. I am a bit confused
th
Hi,
Also please check this .wxs file and let me know if I am doing anything
wrong.
Still I need to create separate installer for the same?
Thanks,
Rahul
-Original Message-
From: rahul.ekb...@sungard.com [mailto:rahul.ekb...@sungard.com]
Sent: Tuesday, June 01, 2010 3:03 PM
To: wix-users@
I had a question about whether a feature is supported and haven't seen any
WiX documentation that really answers my question. Basically I was curious
as to how patches could be installed and supersede each other based on the
base used to create the patch.
For example if I have Product v1.0.3 dir
I had a question about whether a feature is supported in WiX or not. I
haven't seen any WiX documentation that really answers my question.
Basically I was curious as to how patches could be installed and supersede
each other based on the base used to create the patch.
For example if I have Prod
I always use just one base but multiple bases (i.e. targets) are possible from
what I understand from the documentation. I avoid them because that increases
the size of the patch (differences from both bases must be stored in a patch)
but it should work if you declare two targets.
-Original
Here is one example where you can try insert additional targets (bases)
http://schemas.microsoft.com/wix/2006/wi";>
http://www.myco.com";
Classification="$(var.CLASSIFICATION)"
AllowRemoval="yes"
OptimizedInstallMode="yes"
Windows installer caches entries in the Icon table in the installer cache
location as you see below, so in effect by creating that Icon WIX element, you
think of it as if it were a separate File element from your root exe. In the
past, when I've authored COM registration and tried to do what you
A summary of the different behaviors depending on where you schedule
RemoveExistingProducts, and benefits and drawbacks of each in general, can be
found at:
http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx
--
Bryan
-Original Message-
From: Stefan Kuhr [mailto:kustt...@gmx.l
Wix actions can be set into "verbose" mode by setting the property
LOGVERBOSE to 1. (read the comments in the following blog post:
http://www.joyofsetup.com/2008/07/15/verbose-logging-from-wcautil/).
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, Ju
Scheduling RemoveExistingProducts "late" (that is: close to InstallFinalize,
either right before or right after) requires that you are rigorous in
following the famous Component Rules (specifically, you need to make sure
that files named the same placed in the same directory always have the same
GU
I don't mean you have to create an installer specially just for the VSTO part,
I simply mean you have to have an installer to write the proper registry keys
and can't use VSTO Installer's default behavior. You are welcome to have the
installer do more work than just installing the add-in.
When y
The path of the CommonAppData directory is found in the "CommonAppData"
property after CostFinalize. The same with all the entries in the Directory
table.
-Original Message-
From: Joshua Chambers [mailto:jos...@tdronline.com]
Sent: Tuesday, June 01, 2010 12:43 PM
To: wix-users@lists.sourc
"The path of the CommonAppData directory is found in the "CommonAppData"
property after CostFinalize. The same with all the entries in the Directory
table."
Okay, those are properties in the WiX file, no? How can I pass that to my
C# program (custom action) to manipulate the file? I'm confuse
See... what is wrong here? I included a "reference" to the
backupSettingsAction project in the WiX project.
--
View this message in context:
http://windows-installer-
Hi
Another option to trace this is to use SQL Profiler - it should show the calls
being made and any errors occurring.
By setting ContinueOnError="yes" any errors will be swallowed (they may be in
the log). If you are doing this only to make the uninstall robust against the
database not exist
Itzik,
Are you asking if you can use WiX to install an application to Windows Phone
using Active Sync or are you speaking about the creation of a .CAB file for
installation on the phone itself?
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove
On Tue, J
Hi Bryan,
Thanks for reply.
I checked on XP, the hotfix works properly and after changing
EnableLocalMachineVSTO = 1 in registry key the add-ins are visible for other
users too. It means our Wix installer working properly. Now the main problem is
with only the Hotfix on windows 2008 server R2 64
I answered a similar question a while back, this is by design of
Windows Installer to support Advertised installations. It all makes
sense once you read the documentation on the Icon table
[http://msdn.microsoft.com/en-us/library/aa369210(VS.85).aspx] -
specifically the following paragraph:
> The
Windows Installer and Windows does have a way to deal with this
situation... it's called the "Restart Manager" ;)
http://msdn.microsoft.com/en-us/library/aa373524(VS.85).aspx
If you implement restart manager support, Windows Installer can ask
your app nicely to shut down and release the file locks
If you are using Torch and Pyro (with the Patch element) instead of the
PatchCreation element, you run torch additional times to create the
transforms from each target to the Updated build and pass each of the wixmst
files separately to pyro.
The concept is the same: the patch contains multiple tr
$(var.*) syntax refers to preprocessor variables either passed on the
commandline to candle or using the syntax. When using
MSBuild/Votive, projects that are referenced have certain preprocessor
variables assigned from those projects (such as TargetDir, TargetName,
etc.). That set of variables (th
Hi Bryan and Sascha,
So as I understand you (we are not using advertised features), it is not
possible with Wix/MSI to just put the real .exe path in the created shortcut
like all other installers I've tried can do?
The core problem we are faces with is that users drag the desktop icon
created by
53 matches
Mail list logo
