If you want an example of how **not** to do an installer the SQL Server is
the one to go for! It is not the Windows Installer parts that are bad it
is the bootstrapped that warps it all up.
>I had SQL server Express 2012 on my server a few months ago, had to
>uninstall it to clear out some errors
Hi everybody,
May be someone of you could give me a hint how can I correctly use the new
feature to install a vsix package (Visual studio package), for Visual Studio
2012, using http://wix.sourceforge.net/manual-wix3/vs_xsd_vsixpackage.htm I
Have installed wix Toolset v3.7.1001.0 and I add
No worries Rob :)
__
Steven Ogilvie
Sent from my BlackBerry...
3 - 45 Bertrand Street
Ottawa, ON
Canada
K1M 1Y5
Mobile: +1 613 299-2121
E-mail: sogil...@msn.com
-Original Message-
From: "Rob Mensching-7 [via Windows Installer XML (WiX) toolset]"
Date: Fri, 5 Oct 2
Note: there is admittedly some work to clean up the sharing of searches
between MSI and Burn. We have a good first draft but it can be smoothed out
a lot in the future.
On Thu, Oct 4, 2012 at 12:41 PM, Steven Ogilvie wrote:
> Dude... You rock... works like a charm :)
>
> Thank you very much, I ma
Wow, the log file didn't seem to suggest that at all. SQL Server team
really should switch to using Burn for their bootstrapper/chainer.
On Thu, Oct 4, 2012 at 2:00 PM, Nick Ramirez wrote:
> Finally got it to work, after installing .NET Framework 4. I guess the SQL
> Server installer can't do t
What is he doing in his current installer? There are some things in MSI
that are more complex than in InnoSetup and NSIS (although Burn in WiX v3.6
tackles most of them). I'm curious because tackling the complexity
problem/perception is very important to me in WiX v4.0.
On Thu, Oct 4, 2012 at 12:4
It seems a bit unfair to blame MSI for the SQL Server install.
On Thu, Oct 4, 2012 at 6:00 PM, Katherine Moss wrote:
> Thanks; I wish that MSI could prove so simple for users though in some of
> Microsoft's own products. Example? I had SQL server Express 2012 on my
> server a few months ago, ha
Okay, cool. I have a repro of this locally. It's a bug in Burn. Hope to
have fix in next build. Feel free to open a bug to track if you like.
On Thu, Oct 4, 2012 at 3:38 PM, Nick Ramirez wrote:
> Yes, targeting same MSI. The first patch changes an existing text file that
> got installed by the
Thanks; I wish that MSI could prove so simple for users though in some of
Microsoft's own products. Example? I had SQL server Express 2012 on my server
a few months ago, had to uninstall it to clear out some errors, and are you
kidding me? I had to reinstall the operating system to reinstall
MSI is complicated. Setup is complicated. There is a learning curve but
once you nail it, it's easy for your users.
The key to MSI is that it's declarative (functional programming),
transactional and has standardized support for upgrades, patches,
uninstall, repair, silent and so on. Learn h
JAWS and the rest can read the WPF installer just fine, but what concerns me is
the lack of support for keyboard input; to me, I've always thought that
pressing enter and doing a double click with the mouse were the same thing. I
can for instance, install the product, but when there is an updat
I feel your pain. Over the years I have used lots of install technologies,
installShield (script and windows installer), wise (script and windows
installer), inno setup, plain batch files, custom exes, NSIS etc, etc. The only
one that has provided me with a 100% reliable installation is windows
For 2012 I believe it will work with .NET 3.5 or .NET 4.0.
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: 04 October 2012 22:00
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bootstrapping SQL Server 2012 Express
Finally got it to work, after ins
Yes, the server appears to be hijacked. I sent email to the owner of the
server (it's not me).
On Thu, Oct 4, 2012 at 12:31 PM, akonsu wrote:
> http://wix.tramontana.co.hu/tutorial takes me to a viagra site or
> something
> similar. has the server been hijacked?
>
> konstantin
>
> -
Are the two patches targeting the same MSI?
On Sun, Sep 30, 2012 at 9:43 PM, Nick Ramirez wrote:
> The version I have is 3.6.3303.0. I took a stab in the dark and rearranged
> the elements various ways, but couldn't come up with a solution.
>
>
>
> --
> View this message in context:
> http://win
Hmmm "COM is love"? I always thought COM was COMplicated... lol.
-Original Message-
From: tom [mailto:tomer.d...@intergraph.com]
Sent: Thursday, October 04, 2012 3:29 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] I have heard that MSI is too complicated from a
programm
Don't forget validation (ICE's) and support for existing and future platforms.
If you utilize the Burn approach for any (limited) customization to the
installation and simply property drive your MSI's then they become incredibly
simple to manage (over some custom script that may or may not work
Only the Wix BA/UX (not one you can use directly, but you can use it as a
starting point if you are writing your own managed UX/BA) is in WPF. As for
assigning them proper values, it's as simple as assigning the properties a
value. Ex:
News
Could be changed to
I would argue that developing MSI with wix is a little bit more complicated
than developing in c# or other scripting language at the beginning, because
programmers which use to tell the compiler "How to do" things now need to
use declarative language and tell the compiler "What to do"
Some progra
Yeah; I know all about this, though I'll be learning more. And what you said
about VS integration, you guys should develop full integration with VS; all
project types including patches and what not, dialogue editors, and wizards.
But anyway, that's another topic for another day. Well, I don't
I don't know much about Inno, but reasons for us to use MSI include:
- rollbacks
- patches (i.e., replacing less than full files), including with rollbacks
- logging
- integrates with Windows directly
- and, maybe in the future, SCCM connections
- Visual Studio integration (not as important now, bu
Hey Katherine,
For the past 20 years I have been using various InstallShield products,
InstallAware, Wise Studio etc...
When I first found out the company I work for was using WIX I shuddered... but
now after using it for 5 weeks it's pretty good (and free), there have been
some hiccups but th
Hi guys,
Since I am just learning to be a .NET C# programmer, can somebody shed light on
why using WiX over something like Inno would be more complicated and why
programmers are often less compelled to use WiX? I'm asking this because my
friend has got a project he's working on where the main p
Dude... You rock... works like a charm :)
Thank you very much, I made some minor modifications:
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: October-03-12 6:36 PM
To: General discussion for Windows Instal
Thanks, guys. To answer your question, both of them (both the actual WiX
installer and any installers that I create in the future once I get to be a
better coder), should be more screen reader friendly. But that does not mean
that screen readers should have to rely on a standard UI since most
I think you missed my point about WixStandardBootstrapperApplication, this is
the *only* UI that comes out of the box with WiX - the "fancy UI" was written
specifically for WiX, you can use it as a template but you would have to write
the code.
If you want to see what WixStandardBootstrapperAp
Katherine,
Saying it has nothing to do with the language isn't entirely correct. The WIX
BA/UX is written in C# and utilizes WPF. As such, they made a visually
immersive install with lots of "eye candy". When briefly looking at
http://msdn.microsoft.com/en-us/library/aa350483.aspx verses what
Okay, guys,
I don't know how to explain this any further without demonstrating for you the
problem. It has nothing to do with what language the underlying program is
written in, and it has nothing to do with the operating system. Firstly, I
refuse to use alternative UIs that haven't been upda
Is your property all uppercase letters? Making it all uppercase makes it
public, otherwise it is private. Also if the property is being set in the UI
sequence and then being called in the Execute sequence you probably need to add
it to SecureCustomProperties.
http://msdn.microsoft.com/en-us/lib
>From the MSI SDK documentation on TextBox controls, "The property associated
>with the Edit control is only set when the control loses focus. Therefore you
>must tab from the control or select a different control for the property to be
>updated".
-Original Message-
From: Steven Ogilv
Sorry, lets try that again:
DATABASE_WINDOWSAUTHENTICATION="1"
DATABASE_WINDOWSAUTHENTICATION="0"
-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: October-04-12 10:40 AM
To: wix-users@lists.sourceforge.net
Subjec
sigh my original msg is missing text:
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-Disable-a-control-because-another-control-is-empty-enter-text-control-is-not-enabled-tp7581117p7581118.html
Sent from the wix-users mailin
Hi all,
I created a custom dialog...
I have a button control that is disabled/enabled whether or not some text
box controls are empty or have some text in them:
Here is one of my text box controls:
DATABASE_WINDOWSAUTHENTICATION="1"
DATABASE_WINDOWSAUT
Hi I got my custom action to populate my Listbox table in Wix which is
linked to a property. I am now trying to call that property from another
custom action but I do not seem to be able to do that. I'm using
MsiGetProperty and tried WcaGetProperty but I am getting and it is
not picking up the val
SecureCustomProperties in a merge module has always been a problem for
InstallShield. It doesn't properly merge all the properties into a single
property. Frankly I wish MSI had allowed for SecureCustomProperties.Guid (
starts with SecureCustomProperties) to allow for easier merging and use a
While I haven't used Burn yet, I've done a lot of Setup Prereqs in
InstallShield. In general, I like to either a) duplicate my prereq checks
in the chainer and the MSI or put a check in the MSI that enforces that
it was launched by the bootstrapper/chainer. You don't want to get in a
situa
Got it all working...phew...thanks for all your help..:)
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 04 October 2012 13:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Populating Listbox from Custom Action
I'm not s
It is simpler than that:
Neil
>Hi create the image you want using the sizes specified here:
>http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
>
>And add them into your installer like:
>
>
>Height="44"
>TabSkip="no" Text="Banner" />
>
>That is for the banner, the background
I'm not sure what you mean. You might want to check in the project's
properties that you really are compiling for narrow/8-bit/multi-byte chars.
Look under Configuration/General at the Character Set setting. I'm assuming
it *doesn't* say Use Unicode Character Set, which means wide/Unicode
character
A secure (think "trusted") property is one that can be passed from the
UISequence or command line to the execute sequence where presumably it will
have some effect on the changes made to the system. Secure properties must be
public.
A public property is one that is visible to a user and can be chan
Hi create the image you want using the sizes specified here:
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
And add them into your installer like:
That is for the banner, the background is the same method..:)
-Original Message-
From: Chaitanya [mailto:chaita...@poin
Hi,
I want to replace image in WixUI_InstallDir.How to do that..
Please Help me.Im new to Wix.
Tahnks.
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance managem
I tried that but it says that it is not compatible. When I converted
"ComPort" to a Wide char I am having trouble initialising it correctly.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 04 October 2012 12:29
To: General discussion for Windows Installer X
I'd just like a bit of advice/clarification on property types and CAs. If I
write a CA to fetch a folder location from the OS (to be used like
'ProgramFilesFolder') then I need to set a property (correct?) If I use a
private property I have to give it a 'default' value which is overwritten by
t
Since all your other strings seem to be 8-bit characters, delete the "L" from
the front of any literal strings. That will make them 8-bit too.
So L"ListBox" -> "ListBox" and
L"COMPORT" -> "COMPORT"
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 04 Octob
Hi Peter, Me and C++ are not long introduced so please excuse if I am being
really silly. What would you suggest I change? Comport to a Wide Char?
Thanks
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: 04 October 2012 12:10
To: General discussion for Windows
I've had a quick glance and it looks like you're compiling with 8-bit chars
but you've also got L"ListBox" and L"COMPORT" which are wide chars.
-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com]
Sent: 04 October 2012 11:51
To: wix-users@lists.sourceforge.net
Subje
Hi if anyone has a chance would they check out my question on SO as I think
I am near to solving it but need an extra hand. Would greatly appreciate
it..:) Thanks
http://stackoverflow.com/questions/12562643/wix-add-to-listbox-from-c-custom
-action
--
The PYRO message is just warning you that you might get source prompts.
Ignore it for now.
Add a property definition in your upgraded MSI
Build it and try installing the new MSI as a minor upgrade. That will check
for certain kinds of problems and issue an error during the update if found.
Check
This should not be a problem.
On Thu, Oct 4, 2012 at 1:08 AM, Neil Sleightholm wrote:
> Is it possible that SQLEXPR_x64_ENU.exe is a 64 bit process, if it is that
> launching from the 32 bit BA might be an issue.
>
> Neil
>
>
> >I haven't been able to install SQL Server 2012 Express on Windows 7
For anyone that is interested I have published an extended native bootstrapped
application here:
http://neilsleightholm.blogspot.co.uk/2012/10/wix-bootstrapper-application.html.
NOTE: this is *not* a WIX toolset release so please ask questions on the blog
not this mailing list.
Neil
Neil Slei
https://sourceforge.net/p/wix/bugs/3108/
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 04 October 2012 03:32
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding the Secure attribute in a Property fails to
build merge module in 3.6
On 03-Oct-12 06:
https://sourceforge.net/p/wix/bugs/3105/
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 03 October 2012 04:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixLibs do not seem to work after 3.6 upgrade.
On 02-Oct-12 11:51, Hoover, Jacob wrote:
> Well
Thanks Peter. It works.
But one more question, in the patch I've added a new feature and a component
under it.
In the patch metadata I'm not referencing this new component and then also the
component is shown in the diff.
Any clue?
Thanks once again,
Kajal
-Original Message-
From: Peter
Is it possible that SQLEXPR_x64_ENU.exe is a 64 bit process, if it is that
launching from the 32 bit BA might be an issue.
Neil
>I haven't been able to install SQL Server 2012 Express on Windows 7 64-bit
>using Burn. Has someone been successful with this that can point out
>what's
>wrong with my
You are trying to install the x64 version of SQL Express, are you sure you
tested on a x64 Windows? If you were to run this on a x86 (32 bits) system
you're installer will fail with something like the error you mention :)
Best regards,
Albert van Peppen
Senior System Engineer
-Oorspronkeli
56 matches
Mail list logo
