Take a look at ocsetup.exe; on Win2k8 you can run "ocsetup.exe Netfx3
/norestart /quiet" and it will install the feature. Win2012 might be the same
but if it is like Windows 8 you are stuck as the features are not built-in (I
haven't actually installed 2012 yet so don't know).
If it is not ocse
You seem to have iis:WebApplication in your vdir so that may be the issue, I
would write it like this:
Neil
-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 01 February 2013 05:22
To: WiX-users@lists.sourceforge.net
Subje
Have to disable the policy that disables per-user installs on server.
On Thu, Jan 31, 2013 at 10:24 PM, Ravi Raj wrote:
> I have created an installer with following details:
>
> Keywords='Installer' InstallerVersion="405"
> Manufacturer="!(loc.CompanyName)"
> Description="!(loc.
I think someone created a custom exe to handle this scenario in the
archives. Be nice to have a more ideal solution built in but no one has
coded that yet.
On Thu, Jan 31, 2013 at 11:16 PM, Hans ter Horst wrote:
> I didn't see an answer regarding this question and I'm sort of stuck on
> this. Do
What you would have to do is setup the colour of the background and text to the
system colours, there is a magic number for the system colours (WindowText and
WindowBackground if memory serves me right) then the colours would match
whatever the user has selected which is better than you hard cod
I didn't see an answer regarding this question and I'm sort of stuck on
this. Does anybody have an idea how to handle the different way Windows
2012 Server behaves if a prerequisite is defined as a server feature?
Thanks,
Hans
On Wed, Jan 30, 2013 at 1:04 PM, Hans ter Horst wrote:
> Hello,
>
I have created an installer with following details:
Also I have not used any Privileged Custom Action in any process
(InstallUISequence or InstallExecuteSequence ). But when I execute the
installer, the install button shows SHIELD icon. When I click install, i
got a popup that "The system a
Hi,
Iam creating Site in iis.Under the site I want to create an virtual
directory.
But,through my code it is creating an "Application".see the code which I
wrote for creating an Site and virtual Directiory.
Let me know where iam doing Mistake..
Creating Site..
We are using Customized Dialogs for our installer and now when i've created a
custom dialog for the user to select the path to Install the installer fails
with error 2812.
The error description for the code 2812 is "The event[2] is not recognized"
in the Windows Installer Error Message Table.
But
Hm, but Windows (or whatever controls the color inverter) could change it at
any time, such that we'd have to find the new magic
number where the inversion no longer happens.
I think it makes more sense to simply be able to make previously set font
settings overwritable later in the WiX script f
Or you could contribute the fix. Find the magic number that looks black to
humans but isn't black to the color inverter.
On Thu, Jan 31, 2013 at 10:34 AM, The Ouizard wrote:
> Thanks for promptly replying. Hm, most unfortunate if it was actually done
> by someone but not contributed to the mai
Make sure your packages of URLs provided (authored is easiest but you can
programmatically set them all) then return IDDOWNLOAD from the
ResolveSource call.
On Thu, Jan 31, 2013 at 10:30 AM, Bryan Johnston
wrote:
> I have a custom MBA that I have been using and I would now like to make a
> light
The feature tree for each MSI should already be captured in the
BootstrapperApplicationData.
On Thu, Jan 31, 2013 at 10:00 AM, Hoover, Jacob
wrote:
> Not today, but you have the source so it would be possible to
> contribute it as a feature. I'd envision you needing to describe a tree
>
Rob,
The attached txt files are the build output of a the same WiX project.
* Wix3.5 is a 32 bit Vista workstation running VS 2010
* Wix3.7 is a 64 bit Windows 7 workstation running VS 2012
* Both are connected to the same TFS-2012 server and project
This output i
I think there is an issue with Merge Modules/WixLibs/product.wxs... Wixlibs
require you have a directory element in each wixlib that is the same
Then in the merge module I reference that wixlib directory
The wixlibs has the directory element as such (same for each wixlib):
Each of my merge mo
Thanks for promptly replying. Hm, most unfortunate if it was actually done by
someone but not contributed to the main WiX dev.
I'd really rather not have to create my own UI. The WiX_Minimal is perfect,
aside from this text issue, and I'm relatively new to
WiX such that rolling my own is non-tri
I have a custom MBA that I have been using and I would now like to make a
lightweight web bootstrapper which will download the packages that need to
be installed. I thought you would get that for free with the underlying
bootstrapper engine by simply specifying the download url in the bundle,
but I
Not today, but you have the source so it would be possible to
contribute it as a feature. I'd envision you needing to describe a tree
structure in XML, and enhancing the existing schema to support it. From there,
adding a "page" in the BA to build up the tree and display it isn't a triv
Can you have the wix standard bootstrapper prompt the user for feature
selection? I haven't seen it do that . . .
On Thu, Jan 31, 2013 at 11:05 AM, Rob Mensching wrote:
> You can modify feature states via the BootstrapperApplication.
>
>
> On Thu, Jan 31, 2013 at 8:44 AM, Karl Werner
> wrote:
>
I'd see this as a +1 vote for WixStdBA to support a declarative feature tree
dialog. Not a trivial task, but something that would be useful.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, January 31, 2013 11:05 AM
To: General discussion for Windows
It is possible. You can create your own UI. I guess I disagree that it
should be a simple, basic thing provided in the default WixUI. I honestly
thought the WixUI design was to make the text color "almost black" but not
quite black such that high contrast wouldn't pick it up and flip it. Maybe
tha
I've posted this twice already with no response; does no one have any idea how
to solve this?
It doesn't seem outlandish to want to support users who don't use the default
display configuration. Setting/overriding a font color
seems like it should be a simple and basic thing, but I haven't found
Richard is correct. Burn will defer all "restart required" requests until
the end. Only a "force restart" will cause Burn to stop the install,
restart the machine and attempt to resume after that.
On Thu, Jan 31, 2013 at 8:48 AM, Richard Mayes wrote:
> If you use a within the ExePackage for
> t
You can modify feature states via the BootstrapperApplication.
On Thu, Jan 31, 2013 at 8:44 AM, Karl Werner wrote:
> To close the loop on this, I ended up doing the following:
>
> 1) Reverting to the Wix Standard Bootstrapper. (There is probably a way to
> get my custom bootstrapper to work, bu
Hello,
I need some help with my installer script. It is not installing the my fonts
to the FontsFolder.
I don’t receive any errors building the script or installing the msi. The
fonts are not installed the the windows font folder.
Any help appreciated.
I’m running Wix 3.7 with VS2012 and in
If you use a within the ExePackage for
the dotnet installer, then it will have the desired effect. If dotnet is
installed it and the InstallCondition is correct it will skip the
ExePackage element completely and not do a reboot.
This does mean for you Eric you will have to manually include the
Ex
I want to make sure I understand this. Does Wix currently have anyway for a
restart to happen halfway through an install and then continue the install
when the computer restarts? Or is the problem that the .NET install is
doing something in particular that's causing that functionality to fail?
Eri
To close the loop on this, I ended up doing the following:
1) Reverting to the Wix Standard Bootstrapper. (There is probably a way to
get my custom bootstrapper to work, but I exhausted enough time trying to
figure it out. Somehow the Wix Standard Bootstrapper knows what mode to go
into early in
The issue is even more compounded...
I have 5 merge modules, and each merge module has WIXLibs as well
So I have a mergemodule redirect directory element and a wixlibs folder element
i.e.
PRODUCT.WXS
MergeModule.wxs
this would be the path C:\Progr
Take a look at the bundle log and see if something caused those MSIs to be
removed from the cache. Are the MsiPackage elements maybe marked Cache='no'?
On Fri, Jan 25, 2013 at 8:19 AM, Steven Ogilvie wrote:
> Got these errors :(
>
> MSI (s) (C0:50) [20:23:32:105]: Product: Microsoft System CLR T
Yes, the directories are all cleaned up in the end. The question is what is
cleaning up the file that is mentioned in the log file in the middle of the
install. That's what is causing the failure.
On Fri, Jan 25, 2013 at 11:04 AM, victorwhiskey wrote:
> Thanks Rob,
>
> For the 0x80002 issue, are
Understood. It's the part of the path that might be modified that needs to be
preserved. I've seen exactly this behavior when INSTALLLOCATION wasn't
preserved. Talking about the whole directory tree was confusing on my part.
--
John M. Cooper
-Original Message-
From: Rob Mensching [ma
UpdateReplace means use the bundle information provided by a call to
Engine.SetUpdate and launch that bundle instead. Doesn't look like you
called SetupUpdate.
If you want an upgrade, then keep the Bundle/@UpgradeCode constant and make
sure the newer bundle has a higher version.
Note: if you keep
Phil,
Not sure can you be more specific about what you upgraded to and what works
and does not work now.
On Wed, Jan 30, 2013 at 3:10 PM, Phil Rogers wrote:
> Has anyone experiences "LGHT0103" after upgrading from 3.5?
>
> When performing builds in 3.5 light would respect a relative path of the
There is not a way to say "Force restart here if necessary" but I think
there is a feature request open to add such a feature. Sounds like there
is real world need.
On Wed, Jan 30, 2013 at 9:42 AM, Eric Schultz wrote:
> Bob,
>
> That IS what's happening. Is there a way to have it request to rebo
Yep, bug in the build of wix37-binaries.zip file. It's missing some of the
.targets files that should be in there. You can grab them from the
ProgramFilesFolder:\MSBuild\Microsoft\Wix\v3.x\*.targets. Sorry about
that. Be great if you could file a bug so we keep track of the issue.
On Wed, Jan 30
John, you shouldn't have to preserve Directory paths if a Component is
installed in it. You do need to preserve any Property values that you want
persisted.
Steve, sorry, I usually point people to the verbose log file to help them
jump start their investigation. I unfortunately don't have time to
Use a Library project for the common stuff and separate Setup projects to
build the different MSIs. If you want to put all that in one project,
you'll learn *a lot* about MSBuild.
On Thu, Jan 31, 2013 at 6:33 AM, Jacob Baughman wrote:
> I'm new to MSBuild (and WiX for that matter) and I've been
I'm new to MSBuild (and WiX for that matter) and I've been trying to figure out
how to use the wix.targets definitions to set up the installer project for my
.NET solution. The four project output types that come with the Votive Visual
Studio templates work fine, but what I'd like to be able to
Chances are really good that you're not correctly preserving the complete
directory tree where those files are going. In many ways, a patch is just a
repair on one feature. The Windows Installer Service has no memory of your
whole directory tree. Generally, you have to preserve things like
I
The way that works for my projects:
1) make a custom version of the setupexec.vcxproj;
2) modify the resource and headers files to identify and describe your product;
3) I run a custom build template activity that updates the product version
number with the version of the bound product each build
Any idea Rob?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Weird-Repair-happening-tp7583229p7583292.html
Sent from the wix-users mailing list archive at Nabble.com.
--
How can we provide the version info and description info to exe which is
created by 'setupbld.exe'?
I checked all arguments through command line and did not find any.
I tried -title but it is not displaying what the title when I right click the
exe and see it properties on any tab.
While creatin
In your /*\Program Files (x86)\WiX Toolset v3.7\doc/ folder, see WiX.chm for
a good place to start.
If you run into any particular problems, you can always post questions here.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Just-getting-started
44 matches
Mail list logo
