I checked the source repository just now and I managed to update the
changesets.
Thanks
On Fri, Jan 21, 2011 at 6:38 AM, Rob Mensching wrote:
> Should have been up there this morning.
>
> On Wed, Jan 19, 2011 at 10:05 PM, Dandre wrote:
>
> > Hi Rob
> >
> > When will those changes reflect on co
Assignment process is *very* streamlined now. Just email
wixad...@microsoft.com and it's all electronic. You used to have to mail
stuff in (crazy, I know).
Dcoumentation is also very easy to contribute to.
On Thu, Jan 20, 2011 at 6:25 AM, Christopher Painter <
chr...@deploymentengineering.com> wro
Windows Installer always sets Privileged because people used it wrong more
often than right.
On Thu, Jan 20, 2011 at 1:54 PM, Alex Ivanoff wrote:
> Windows 7, UAC is off, user is not an administrator, Windows Installer
> sets Privileged and AdminUser properties no 1:
>
> MSI (c) (08:8C) [15:45:57
Hmm, I don't remember that being necessary. I think the Windows Installer
remembers folders correctly to handle uninstall. Have you seen it not work?
On Thu, Jan 20, 2011 at 5:36 PM, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com> wrote:
> Should we use the "Remember Property" pattern to
I'm not sure how you exclude your default config file changes with PatchWiz,
but then again I gave up on PatchWiz after it hung my build system one too
many times.
-Blair
-Original Message-
From: Aaron DeMarre [mailto:adema...@gmail.com]
Sent: Thursday, January 20, 2011 12:36 PM
To: Gene
Ahh, heh, yeah, I got that backwards. Bummer. Yeah, that should work. Feel
free to open a WiX v3.6 bug and it might get fixed there (or WiX v4).
On Thu, Jan 20, 2011 at 5:56 PM, Murray H wrote:
> Hi Rob,
>
> Other way around. I want to harvest c# projects into a wix library, which
> will then be
WiX v3.5 is basically:
* Visual Studio 2010 support
* IIS7 Custom Actions (without II6 metabase compatibility)
* Minor improvements to language (i.e. MajorUpgrade element)
* More bugs fixed than WiX v3.0 (if you haven't seen the bugs, you probably
don't care ).
On Thu, Jan 20, 2011 at 6:28 AM,
Please post a feature request on SourceForge against v4. In-build harvesting
improvements have been directed towards v4 in an effort to wind v3 down and
get it out the door.
Blair
-Original Message-
From: Murray H [mailto:w...@seravy.com]
Sent: Thursday, January 20, 2011 5:57 PM
To: Gene
Should have been up there this morning.
On Wed, Jan 19, 2011 at 10:05 PM, Dandre wrote:
> Hi Rob
>
> When will those changes reflect on codeplex?
>
> Thanks
>
> Sent from my iPhone
>
> On 20 Jan 2011, at 7:43, Rob Mensching wrote:
>
> > We took a couple last minor bugs to WiX v3.5 yesterday and
Yea, sorry, that's true, isn't it. Sorry, I validate (including calling
DoAction to call CAs that assist in my validations) and then SpawnDialog to
report/or-otherwise-deal-with errors or NewDialog to move on, depending on
the results of my validation. I hadn't tried a warning.
-Original Messa
Well I think I have figured out why the issue is occurring.
The call that is failing in the custom action is LoadUserProfile(). This
needs the SeBackupPrivilege which the windows installers service *does not*
have on a UAC-enabled system.
Some details:
http://blogs.msdn.com/b/vistacompatteam/arc
Hi Rob,
Other way around. I want to harvest c# projects into a wix library, which
will then be consumed in the normal manner by a wix product.
Program c# Projects > Harvested reference into > Program 1.wixlib >
Referenced in > Program suite.wixproj
This scenario does not currently work. Using a c
Should we use the "Remember Property" pattern to remember DirectoryIds like
INSTALLLOCATION?
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Property-pattern
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
Windows 7, UAC is off, user is not an administrator, Windows Installer
sets Privileged and AdminUser properties no 1:
MSI (c) (08:8C) [15:45:57:221]: MSI_LUA: Setting AdminUser property to 1
because this is the client or the user has already permitted elevation
MSI (c) (08:8C) [15:45:57:221]: PROP
Thanks for the info. I played around with this a bit, but still could not
get a patch I was happy with. I switched to the patchwiz.dll process and it
is giving me the behavior I expect when adding new files to the patch.
-Aaron
On Tue, Jan 18, 2011 at 8:54 PM, Blair wrote:
> As I understand it,
Hi Users,
I am working on a product that needs to support Windows 7 w/ UAC enabled.
The MSI has a few custom actions that perform various configuration items
that I would like to keep contained within the MSI/product install.
The custom actions are Execute='deferred' with Impersonate='no' and the
Some of the MSFT-supplied ICE tests use VBScript (most use C/C++ native
code).
2738
Could not access VBScript run time for custom action [2].
http://blogs.msdn.com/b/heaths/archive/2007/05/31/windows-installer-errors-2
738-and-2739-with-script-custom-actions.aspx
Could also be related to an ant
Hi,
Is there any way to have a ini file only be written and never removed
even on rollback?
Here is the snippet
I have tried both the default afterInstallValidate
and
An uninstall does not remove the ini, which is desired, but if the user
cancels late enough the rollback removes the in
I also seem to get 2 log entries for the same thing:
Action ended 08:01:24: CostFinalize. Return value 1.
MSI (c) (7C:10) [08:01:24:535]: Skipping action: SetCONFIGREQUIRED (condition
is false)
and
Action ended 08:01:43: CostFinalize. Return value 1.
MSI (s) (5C:2C) [08:01:43:067]: Doing action
tell me about it. I've just tried $cWIAServices=3 and I still get the property
set to "1" when that component isn't being installed.
I must be missing something but I can't think what.
-Original Message-
From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com]
Sent: 20 January 201
Conditions
$cWIAServices=3
and
&feWIA=3
should work correctly.
Maksim
-Original Message-
From: Simon Topley [mailto:simon.top...@mwhsoft.com]
Sent: Thursday, January 20, 2011 1:03 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Set property from feature
just to clarify t
Per my comment on your blog, the 3.0 / 3.5 side by side with Votive is an issue
for us. I'm trying to consider ways to mitigate it and it would be helpful to
get a ReleaseNotes style bulletin the highlights the benefits of 3.5 that make
it worthwhile to consider the upgrade.
For me, we are hap
I'd be willing to help with the doco, do you think it would work out? I had
this impression from past threads that it was very difficult to get IP
assignment agreements in place and to get the diffs accepted if you didn't work
for MSFT on the West or East team. If I'm wrong and you'd accept
If you don't want to generate another file (this is what WiX does), then my
new favorite trick is to do:
Product/@Version="!(wix.FileVersion.SomeFileIdInYourMsi)"
On Thu, Jan 20, 2011 at 3:31 AM, David Watson wrote:
> I should also say that in our build process a list of .cs files are updated
>
So I finally got this working and thought I'd best post the reply here for
other people having the
same issue. Specifically, the dirver I'm installing is a file system driver.
Here's my INF file:
-- START OF FILE
---
; Copyright
I should also say that in our build process a list of .cs files are updated
automatically from the master build number.
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: 20 January 2011 11:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-u
On Thu, Jan 20, 2011 at 10:21 AM, Dandre wrote:
> assemblyinfo.cs files and update the version numbers. Then using a wix
> include file using the variable holding version 1.0.0.0 we update that
> file and so all installers referring to that include file will get
I was hoping to avoid generating y
Hi,
Our builds run a custom TFS build task that checks out a build number file,
updates it and checks it back in.
This is used as a msbuild property that is passed to our wixprojs which are
built from a .sln.
In the 'Define preprocessor variables' setion in votive we have a mapping
from msbuild "b
just to clarify that this doesn't work for me if I use the component state
instead of the feature state
Simon
-Original Message-
From: Simon Topley
Sent: 19 January 2011 18:10
To: 'wix-users@lists.sourceforge.net'
Subject: RE: Set property from feature
sorry the first one of them uses t
Hi Rune
I haven't checked your links but what we use is the Tfs build server's
ability to download the new source from repo, look for all
assemblyinfo.cs files and update the version numbers. Then using a wix
include file using the variable holding version 1.0.0.0 we update that
file and s
I have googled my eyes out recently, trying to figure out an easy way
of setting my installer's version number to match that of my product.
I found three alternatives. None of them appeals to me, because they
are either kludgy, involves some kind of plug-in or ...well, kludgy:
http://morten.lyhr.
31 matches
Mail list logo
