Since I know that everything I'm installing is managed code anyCpu build output
I enabled this with my service deliverable wix sources using the following
syntax.
Hi all,
I am facing a problem in populating data into ListBox.
I am using 2 buttons viz., " Add" and "Remove" to insert and remove Values
into ListBox.
I am calling a Custom Action to achieve this.
After Adding few values into ListBox. If i try to remove any element in the
ListBox and then try
Ok, this is pretty straightforward then. In your postbuild step where you're
using bin\$(Configuration) change it to this:
$(TargetDir)%(EmbeddedResourceWithCulture.Culture)\$(TargetName)$(TargetExt)
It's pretty long but will translate into the full path of each MSI produced by
the build. You c
Correct. Currently only have a reason to have a macro value for full path of
msi files output in postbuild step. Prebuild processing currently only
involves strong name signing and sandcastle chm file generation prior to msi
build that uses those bits.
-Original Message-
From: [EMAIL P
Hi,
I want to create one common installer that will work for 32 Bit and 64 bit OS.
How can I do this?
Regards
Sandeep
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux ba
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 11, 2008 6:35 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] getting working v1.0 -> v1.0 minor update using msp & msi
solutions
Thanks for all the responses to my recent questions associated with getting
working v1.0 -> v1.0 minor update using msp & msi solutions pulled together.
At this point I believe I have what should be working sources and build output
to carry out a minor upgrade using both the msp & msi approaches
Robert,
One follow-up question: do you need to know the path to the MSI files in the
prebuild step? From what you write below it sounds like you only need it for
postbuild. Prebuild is only about signing the assemblies that go into the MSI,
correct? (It is very easy to give you the full paths t
I haven't found a way to do it with a single msi that is supported. The
approach I take is to not embed the files in your MSI but put them in an
external cab file. Then I build each language variant, as they only contain the
install code and not the files they tend to be quite small. I then use
I've found the MsiBreak environment variable is a very useful tool for
debugging custom actions. See
http://msdn.microsoft.com/en-us/library/aa368264.aspx for the details, but in a
nutshell:
1) Start a command prompt (if you are on Vista make sure it is elevated. XP
make sure you are an admin)
I often encounter problems debugging deferred C++ DLL CAs. Most of the
time DebugBreak() works. Now and then it won't and then I use __asm {
int 3 } which, for some reason, tends to work more often than
DebugBreak.
Then I encounter situations when even int 3 won't work in the sense that
Vista (an
Ok. Let me think about this tonight, there are likely a couple of solutions to
this that will work.
Neil
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien
Sent: Thursday, September 11, 2008 2:27 PM
To: 'General discussion for Windows Install
Using Wix 3.0.4318. I built an installer based on WixUI_InstallDir. Running
msiexec /qf /x [ProductCode] does uninstall the product correctly, but the
progress dialog makes it look like it is actually installing it. It appears
WixUI_InstallMode isn't set to "Remove" like it should be. Am I ove
I found a workaround. Open the Wise generated MSI with orca and right click
on the CustomActions table and select "Adjust Schema" now add a new column
at the bottom called ExtendedType (Short Int, Nullable). Now you should be
able to use dark on the msi. You may want to remove the other Custom ta
Hello All,
Anyone has an idea about how to check Windows Installer Runtime Version
in Wix v3 as an install condition? Thanks for help.
Jason
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challeng
I have been having problems trying to install a service. I am the admin user
in this machine but I keep getting permission problems. I am using WIX
3.0.4429.0
Without the tag and the tags it works
perfectly.
I added serviceConfig and then PermissionEx to try and solve permission
issues with
In article <[EMAIL PROTECTED]>,
Rob Mensching <[EMAIL PROTECTED]> writes:
> Services don't get logon rights. Users do.
True, but services do run as a particular user. By default this is
"system" IIRC, but its a gigantic security hole to run your services
as system. Best practice is to cr
Like pretty much everything else that looks like it works but isn't officially
approved is due to the fact that "it" doesn't always work correctly. I do not
remember the specific case here but I'm pretty sure it had to do with some UI
cases.
Anyway, using features that aren't documented to wor
If I create a wix vs08 project containing a single Product.wxs with patch
content and build I get one warning but otherwise it all builds.
When I look at the underlying candle and light commands they pretty much are
exactly the same as the chm "Using Patch Creation Properties" outlined candle
a
Services don't get logon rights. Users do.
Why are you installing a service with a CusotmAction? The Windows Installer
supports that natively.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yu, Brian
Sent: Thursday, September 11, 2008 09:39
To: Genera
Thanks.
I feel like my "spidey-sense" has been ripped out through my spine. I barely
know which way is up right now.
But the future is incredibly cool.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Lewis
Sent: Thursday, September 11, 2008 11:
In prebuild events I execute a custom process that carries out a process that
does full signing of all assemblies that were built using public key only delay
signed build output.
In postbuild events I execute a custom process that carries out publisher
signing of msi build output. I also execu
I am a newbie to Wix, I was trying to do the same this which you have
discussed a long time back.
I am facing problem when i put a check of VersionNT inside Condition
Element.
My code looks like this:
VersionNT >= 501
and when i run it on Windows NT this condiotion newer comes as true.
Than i
I believe it is the first time a given 'Product Code' is installed (not 100%
certain).
I didn't believe that the FindRelatedProducts and RemoveExistingProducts
actions had much of anything to do with a small update or minor upgrade
delivered via an MSI because these scenarios are still reinsta
Sorry, my mistake. I looked at my changes to the WiX build process and you'll
get the different output locations any time you have a localized build (one
that has .wxl files in it).
What are you trying to do in your Pre- and Post-Build steps? Depending on what
you are doing there may be existin
Scratch that question I tried removing the Culture="en-us" attribute and saw
that it is not optional. So it seems that with the current wix framework the
moment you add Resources\Strings.wxl file to your sources
you can expect build output to start showing up in
bin\$(Configuration)\.
-
Thanks for the response. I currently only have a single Resources\Strings.wxl
in my project settings which has the Culture="en-us" attribute set. Should I
just remove that string resources file Culture attribute setting to get build
output landing in bin\$(Configuration) again?
http://schemas
Based on some earlier dl responses I'm currently testing the following syntax
to see if it accomplishes automatically setting the desired REINSTALL and
REINSTALLMODE property values for both msp and msi minor upgrade processing.
Not finalized yet whether it works or not.
Robert,
This happens when you have multiple .wxl files in your project with different
cultures in them. Setting the Cultures field in properties will control which
languages get built, but the output will still go into the sub-folder (this is
so you can set up different configurations, for exam
This is really got me in a tail spin.
In my existing project started with 4004 and recently migrated to the latest
wix drop regardless of whether I do or do not have a | properties
| build | cultures field value specified my light.exe output is getting
directed to bin\$(Configuration)\en-us.
Thanks for the responses.
When folks on the dll state that FindRelatedProducts and RemoveExistingProducts
"only runs the first time the product is installed" do they mean only the first
time a specific msi version of a product is installed? Put another way if I
having nothing on the system and
FindRelatedProducts:
http://msdn.microsoft.com/en-us/library/aa368600(VS.85).aspx ... only runs the
first time the product is installed. As so, I don't believe it executes during
a patch scenario (so it wouldn't be relevant).
That is also documented as being true for RemoveExistingProducts (o
CHarker wrote:
>
> Also I did notice that if I put "Administrators" in the it
> installs the service, fails the config, and then fails to rollback because
> I no longer have permission to uninstall system services!!
>
> the only way out for that was to remove the services registry entry,
> re
How do u grant logon rights to services created by custom actions?
Not
Installed OR REINSTALL
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the cooles
Does inclusion of msi minor upgrade wix sources in v1.1 msi block the ability
to also generate patch msp minor upgrade msp wix sources?
For example does having the following product.wxs sources prevent me from also
being able to generate a v1.0 -> v1.1 patch msp minor upgrade msp wix sources?
Hi,
I'm pretty new to all that MSI stuff, so correct me if I'm wrong.
It's about tasks from the gaming extension. The manual says Play tasks
result in Shortcuts. These shortcuts are part of the component the game
executable is in - necessarly, since a must go below a .
Now, from what I gathered,
Hi Rob,
Thanks for the fast reply, I think WiX is great and look forward to the
continuing developments.
I hope the first few days with the LiveMesh team are going well.
All the best,
Paul
Rob Mensching wrote:
> Burn is a thing that I dreamed would make it in WiX v3.0 but it didn't
> (http://
It appears like it does. Try it out.
On Thu, Sep 11, 2008 at 1:32 PM, derekj <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Does adding the user to the IIS_WPG also do the > aspnet_regiis -ga
> [domain]\user?
>
> regards
>
> Derek
>
> cemiles wrote:
> >
> > Yes. If all you're having trouble with is fi
>wondering if you know where I can find information on amending the condition
>so it only fires on install and not on install.
* I'm assuming you mean only potentially fire on install and never fire when
installed, if so, try this condition...
>DATABASEIPADDRESS OR Installedmailto:[EMAIL PROTEC
On Wed, 10 Sep 2008 12:47:57 -0700, Jeb Remus wrote:
Jeb,
> I understand how WIX can generate N installer for N different
> language files, which is really great. I was wondering however if
> there is any functionality to combine N language files into a
> single installer, that would detect user
Thanks very much
John Nannenga wrote:
>
>>wondering if you know where I can find information on amending the
condition
>>so it only fires on install and not on install.
>
>
> * I'm assuming you mean only potentially fire on install and never fire
> when installed, if so, try this condition...
If you're installing a service you don't need InstallUtil.exe. Use the
ServiceInstall and ServiceControl features in WiX.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sandeep Gautam
(HCL Technologies Ltd)
Sent: Tuesday, September 09, 2008
Hi,
Does adding the user to the IIS_WPG also do the > aspnet_regiis -ga
[domain]\user?
regards
Derek
cemiles wrote:
>
> Yes. If all you're having trouble with is figuring out how to add to the
> IIS grp...
>
>
>
>
> Then just groupref that Grp_IISWPG inside your User element.
Jeb Remus wrote:
> I understand how WIX can generate N installer for N different language
files, which is really great. I was wondering however if there is any
functionality to combine N language files into a single installer, that
would detect user or system locale at run time. Any help or point
In article <[EMAIL PROTECTED]>,
Bob Arnson <[EMAIL PROTECTED]> writes:
> Richard wrote:
> > Where is this extension documented? I get a file not found when
> > attemping to access this URL.
> >
>
> In WiX.chm. The schema namespace is just for uniqueness.
OK, looking at the element, it
http://msdn.microsoft.com/en-us/library/aa369297(VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa370858(VS.85).aspx
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of derekj
Sent: Thursday, September 11, 2008 12:02 AM
To: wix-users@lists.sourceforge.n
Burn is a thing that I dreamed would make it in WiX v3.0 but it didn't
(http://robmensching.com/blog/archive/2008/06/06/Proposed-adjustments-the-WiX-v2-and-WiX-v3-roadmap.aspx).
Since then Bob and I have kicked things about a little and now we are thinking
about making it the focus of a WiX v3.5
Hi All,
I know there must be a way to do it. I am using following Command.. to
create Wxs file as per the directory structure and files.
heat dir -ag -ke -nologo -sreg -sfrag c:\temp\bin -out c:\test1.wxs
Below is the Birectory Structure.
C:\Temp\Bin (4 files at this location)
Hi,
Refer to the attached image.
In a registry entry, we can have many Registry Values for a key.
For example, I have 3 values for the key Softwares\Microsoft\Microsoft SQL
Server\Instance Names\SQL.
I don't know the "Names" of these Registry Values and I want to check every
Values of this key
Hi Folks,
I'm quite new to WiX and I'm looking at using it to build an install
project that requires chaining a couple of simple MSI's together.
I've read a little about the Burn Bootstrapper, and that it has been
dropped from the WiX v3 roadmap.
http://sourceforge.net/mailarchive/message.php?
Yes. If all you're having trouble with is figuring out how to add to the
IIS grp...
Then just groupref that Grp_IISWPG inside your User element.
Are you trying to do more than that?
On Thu, Sep 11, 2008 at 5:37 AM, derekj <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am using WIX 2.0
Great!
That was exactly what I needed!
Thanks a lot again
Daniel
Pally Sandher wrote:
>
> You can use Conditions on your Features to set the Level.
>
> e.g.
>
>
>
>
>
>
>
>
>
>
>
>
> If you ran your MSI as "msiexec /i myproduct.msi INSTALLELEVEL=2000
> ONLYB=true" it
You may also be able to make use of the following properties:
http://msdn.microsoft.com/en-us/library/aa367536(VS.85).aspx
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Pally Sandher [EMAIL
PROTECTED]
Sent: Thursday, September 11, 2008 8:46
You don't even have to that much. WiX includes a library to do this for you,
which you can just include and then reference the property with a .
See the How To: Check for .NET Framework Versions in the WiX CHM file for the
general approach, but substitute in WixVSExtension instead of WiXNetExten
Hi,
I am also is the Same exact Situation in which you are, I am using Heat to
generate the Fragment file to be able to include in my Build which has to be
dynamic , so i foudnt eh best way to do it by using heat, but , i manually
had to update the file and add directoryref tag and Also change th
Hi,
I am also is the Same exact Situation in which you are, I am using Heat to
generate the Fragment file to be able to include in my Build which has to be
dynamic , so i foudnt eh best way to do it by using heat, but , i manually
had to update the file and add directoryref tag and Also change th
You can use Conditions on your Features to set the Level.
e.g.
If you ran your MSI as "msiexec /i myproduct.msi INSTALLELEVEL=2000
ONLYB=true" it would only install Feature B as Feature A would have it's
Level set to since the public Property ONLYB has a value assigned
1. As Bob says on the post you linked, you need to write a chainer for
this functionality as it is not supported by the Windows Installer.
2.
...
3. It depends on your upgrade. I've released 1.0, 1.1 & 1.2 MSI's of one
of our releases all of which upgrade fine using correctly authored
Upg
Hello,
I'm just wondering if it is possible with MSI and with Wix to have 2
features and to choose via msiexec command line which of the two features
should be installed. If I give a feature a "Level" attribute in Wix msi
installs everything with a feature LEVEL <= the specified INSTALLLEVEL. Bu
Hi,
I'm pretty new to all that MSI stuff, so correct me if I'm wrong.
It's about tasks from the gaming extension. The manual says Play tasks
result in Shortcuts. These shortcuts are part of the component the game
executable is in - necessarly, since a must go below a .
Now, from what I gathered,
There's a "How To:" in the WiX 3.0 documentation which describes how to
create shortcuts without any problems.
Palbinder Sandher
Software Deployment and IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrat
Is there any way i can use and elements to
deal with a Jetty-Service?
I see that to register and start the jetty service,we should use the
following command lines:
To register:
Jetty-Service.exe -i jetty-service.conf
To start:
Jetty-Service.exe -t jetty-service.conf
I'm thinki
Hi all,
The problem that I am currently facing was,
I have two msi s, say AppA and AppB. AppB requires AppA to be installed on
the target machine ( treat AppB as some plugins, with out having base
application installed on the machine, having plugins is meaning less). To
verify this dependency,
Hi there
I've set up 3 msi. One base install(309) and 2 minor upgrades (499 and
599)
I expect that 599.msi can only br run when 499 is previously patched.
However, I am able to run 599.msi straight after installing 309.msi
How do u specify this range?
309.wxs
4
The shortcut points to the keypath of the component.
Just use the component of your main shortcut, that is always either
installed or uninstalled and that the app won't function without, or if
you like you can set multiple RemoveFile entries for each shortcut
Component. So long as the FileName col
I am facing the same problem as described here:
http://blog.benday.com/archive/2007/08/09/23155.aspx
Now that I split each file into one component, I face another problem,
since all components are place into one folder I created. I am in a
dilemma to put the tag.
Can anyone help me out? Thanks.
Hi,
I am using WIX 2.0
I have created a cmd line MSI to install an asp.net 2.0.
I created an apppool with a user
I need to add this user to the IIS_WPG group, log on as service and ASP.Net
2.0
eg
aspnet_regiis -ga [domain
Hi,
I am using WIX 2.0
I have created a cmd line MSI to install an asp.net 2.0.
One of the parameter inputs is the IP address of the respective application
database.
I would like to update my connections.config file with this IP eg of config
I have seen examples where the wix user is updatin
Hello,
I try to install VS.NET templates as part of the setup package.
To do that I first read the path to VS.NET:
Then try to install the templates using:
Indeed, Wix compiler providers the error:
The DirectoryRef/@Id attribute's value,
'[VSNET20
You need to have a directory with an Id the same as the property, then have the
sub-directories as
child elements. When the property changes, all the sub-directories will get
updated as well.
Rob
Sergey Abakumoff wrote:
> Hello,
> I try to install VS.NET templates as part of the setup package
Hi,
thanks for your help,
wondering if you know where I can find information on amending the condition
so it only fires on install and not on install.
regards
Derekj
John Nannenga wrote:
>
> Launch conditions fire when the condition is false:
>http://msdn.microsoft.com/en-us/library/aa3
71 matches
Mail list logo
