staller XML
toolset.;
Reply-To: chr...@iswix.com,
"General discussion for Windows Installer XML toolset."
Subject: Re: [WiX-users] .NET config best practices
Sadly this is a huge huge hole / disconnect between how MSI works and how
XML works. MSI treats a Registry Value
3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: jhennessey [mailto:jack.hennes...@hyland.com]
Sent: Tuesday, January 24, 2012 6:00 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] .NET config best practices
My suggestion is that you store this informati
My suggestion is that you store this information in some soft of database and
have the application (or a configuration application ) manage the settings.
I think you'll find it difficult to be able to try and save / merge all this
data as time goes on.
--
View this message in context:
http://wind
sts/2010/5/2/The-WiX-toolsets-Remember-Proper
ty-pattern ) but it really doesn't scale to an application driven but
boatloads of XML.
From: "Richard Martin"
Sent: Tuesday, January 24, 2012 4:15 PM
To: wix-users@lists.sourceforge.net
Su
I'm confused about best practices to use when deploying and maintaining
.NET *.config files via MSI. Our app uses the UnityContainer to manage type
injection and type configuration, some of which is environmental, meaning
type config changes at each customer site. This Unity configuration is
stored
5 matches
Mail list logo