If you give it a fallback option to English it should work e.g.
cultures=ja-jp;en-us.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com
From: Vidya Kukke [mailto:vku...@windows.microsoft.com]
Sent: Thu 15/01/2009 23:34
I have played with this and it works. And it also seems to work for
multiple instances.
Though if you know about any reef in this area, I would appreciate
another hint.
Thank you.
-- Yan
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Friday, January 16, 2009
I have created sample project with votive for VS 2008.
The project contain 2
files
Common.wxi
?xml version=1.0 encoding=utf-8?
Include
?define
Test=Test?
/Include
Product.wxs
?xml version=1.0 encoding=UTF-8?
?
Include Common.wxi?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
It seems that the custom variables defined in a certain file can be
referenced within this file only.
If you want to have a global variable to reference throughout your
project, define it as a parameter to candle.exe (or, if you're using VS,
right-click your project, choose Properties, switch to
1. That isn't true. ?include? essentially makes one big file. This should
work.
2. Try getting the output after preprocessing and see what the variables look
like. Most likely something isn't what you think it is:
candle your.wxs -p
-Original Message-
From: Yan
OK that is the case, but then I need to set a completely bogus keypath
and I can't see how I can actually do that.
I tried pointing it to a registry key that is deleted on install but wix
fails to compile the msi.
-Original Message-
From: Rob Mensching
Sent: 01 December 2008 16:59
Hi All,
I have an install which stops and starts the
ReportingServicesService.exe service during the course of the
installation. The problem I am running into is this:
When the server in question has more than one instance of SQL Server
Reporting Services installed, there is more than one
Hi,
I am trying to add dialog for choosing Start Menu folder for installed
application.
I want it to be to BrowseDlg, but it should be limited only to StartMenu
folder locations.
Any ideas?
--
This SF.net email is
kiyonaka.watan...@jp.yokogawa.com wrote:
Is there any way to localize by the current UI language dynamically?
Or I must specify one language and be linked (light.exe) one by one?
Windows Installer doesn't support multiple languages in one MSI. The
closest is to have a language-neutral MSI
Peter Oehlert wrote:
I was wondering about that given the name. I'm not seeing an execxmlconfig
in the logfile with the /l*v option. Why might the schedule run but not the
exec?
It won't call ExecXmlConfig if there was nothing to do, or if the
component tied to the XmlConfig isn't being
Adam Langley wrote:
Custom Action=RegisterService After=InstallFiles1/Custom
Custom Action=RollbackRegisterService Before=InstallFiles1/Custom
Rollback CAs need to be scheduled before the deferred CAs they roll
back. So you want to use Before=RegisterService.
--
sig://boB
Krzysztof Jakubczyk wrote:
I am trying to add dialog for choosing Start Menu folder for installed
application.
I want it to be to BrowseDlg, but it should be limited only to StartMenu
folder locations.
MSI doesn't offer the option to limit directory browsing to a particular
tree.
--
The component in the InstallValidate step seems to be installing.
MSI (s) (44:E0) [09:54:07:298]: Component: GuidanceExplorerEXECONFIG;
Installed: Absent; Request: Local; Action: Local
Also, I thought components had to be completed together or not at all. The
thing is the xml file gets laid
:-).
One last thing, I was wondering how come if it has not been localized in
japanese I get warnings only for a few strings? Is it that these are new and
have been introduced only in 3.0 but the rest of the strings were in 2.0 and
are available for use as-is in 3.0?
Can you please help
Hello-
I need to launch Web Application on the IIS 6.0 (Windows Server 2003)
where .Net Framework 1.1 and 2.0 both installed.
This application has been developed to be run in .NET 2.0, however by
default it fails as it tryies to run in .NET 1.1
As a workaround we re-link each
Might be helpful
Property Id=ASPNETISAPIDLL
DirectorySearch Id=AspnetIsapiDll
Path=C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 Depth=1
FileSearch Id=AspnetIsapiDll LongName=aspnet_isapi.dll /
/DirectorySearch
/Property
WebApplicationExtension Extension=ad CheckPath=yes
I am using WiX v3, so I'll give this a try. I haven't heard of binder
variables, so I'll go look them up.
One other issue is that of the msi filename itself. I would really like to
be able to use a variable in the OutputName field, so I could do something
like:
I should mention - when I say it built ok, I mean it compiled without
complaint, but there was no version. It was just my_cool_software.msi
So I'm not sure if variable substitution works and I haven't put the setting
of filever in the right place, or variable substitution does not work for
output
I think there were a whole lot of translations provide by someone
(possible Microsoft) in the early days of the UI but they haven't been
update to include the custom actions or additions to the UI.
Neil
-Original Message-
From: Vidya Kukke [mailto:vku...@windows.microsoft.com]
Sent: 16
With WCF in IIS, there has been need to bind net.tcp and others as site
bindings. As far as I can tell, we only have support for http and https right
now. Is this something that is coming or should I create a feature request?
Thanks
Pierson
Is it possible that your VerifyPath is already true so there was no work to do?
-Original Message-
From: Peter Oehlert [mailto:poehl...@securityinnovation.com]
Sent: Friday, January 16, 2009 10:24
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users]
I've never heard of this before. Is that an IIS7 feature? Definitely a
feature request.
-Original Message-
From: Pierson Lee (PIE) [mailto:pierson@microsoft.com]
Sent: Friday, January 16, 2009 13:59
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
From the MSDN documention for RemoveExistingProducts
(http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx):
The RemoveExistingProducts action must be scheduled in the action sequence
in one of the following locations.
...
-After the InstallFinalize action. This is the most efficient
Sounds like Component Rule violations. Did you keep your Component/@Guids
constant appropriately?
-Original Message-
From: vexilar [mailto:s...@sorna.com]
Sent: Friday, January 16, 2009 15:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conflict of Interest: InstallFiles
24 matches
Mail list logo
