13 21:43
Aan: 'General discussion for Windows Installer XML toolset.'
Onderwerp: Re: [WiX-users] Wix dev and regular dev best practices
+1
The chasm between getting things working in a development environment and
getting them working seamlessly in the deployment environment (by end u
: May 31, 2013 15:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix dev and regular dev best practices
If it doesn't get built, it won't get tested. Period.
Dev's have a tendency to consider installer building a waste of time (they
always th
.com
-Original Message-
From: Drake, David [mailto:david.dr...@wizards.com]
Sent: Friday, May 31, 2013 1:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix dev and regular dev best practices
Albert,
Do you require your regular code writing devs
uot;
> OutputPath="$(OutputPath)" Path="..\..\Bootstrapper" />
>
> Mark Freedman
>
>
> -----Original Message-
> From: John Ludlow [mailto:john.ludlow...@gmail.com]
> Sent: Thursday, May 30, 2013 5:53 AM
> To: General discussion for Windows Insta
"$(OutputPath)" Path="..\..\Bootstrapper" />
>
> Mark Freedman
>
>
> -----Original Message-
> From: John Ludlow [mailto:john.ludlow...@gmail.com]
> Sent: Thursday, May 30, 2013 5:53 AM
> To: General discussion for Windows Installer XML toolset.
>
tPath)" Path="..\..\Bootstrapper" />
>
> Mark Freedman
>
>
> -Original Message-
> From: John Ludlow [mailto:john.ludlow...@gmail.com]
> Sent: Thursday, May 30, 2013 5:53 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [
neral discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix dev and regular dev best practices
We're looking at simply making WiX part of the toolkit you need to build our
solutions. We've tried this with some smaller projects and it's worked really
well. De
We're looking at simply making WiX part of the toolkit you need to build
our solutions. We've tried this with some smaller projects and it's worked
really well. Developers can follow up on their own impacts, and they can
tell when they've broken the install. This increases build quality and
frees
I don't know if our approach will work well long term since we are still
developing all of this, but we decided we'd build front end utilities for
developers to use with presets implicitly written out to wxs for them (like
Manufacturer and expected directories to install to, etc.). This way in
9 matches
Mail list logo
