rce control and Jenkins as our build server.
Good luck!
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Thursday, January 26, 2012 3:34 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch building with Torch, all .NET assem
For future readers, this sentence from my last email looks to be wrong: "We
fully-sign our assemblies after they are built, so we might have to make
sure MSBuild is looking at pre-signed copies or it might rebuild them."
I tried fully signing the outputted DLL and did another Build, and MSBuild
di
That's a good thought, so I checked and verified that leaving the file's
version number the same between builds still produces different binary
files.
Unless we hear a better suggestion we're going to try this: Each time we
build an assembly we will leave all the intermediate files in place (.pdb
com]
Sent: Thursday, January 26, 2012 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch building with Torch, all .NET assemblies
"changed"
My initial guess is that your assembly's versions are changing between builds.
I'm very in
My initial guess is that your assembly's versions are changing between builds.
I'm very interested in a proposed approach to this as we have a build that
results in changed versions on every build. I haven't personally investigated
an approach to handle this yet. I haven't had the time yet to do
5 matches
Mail list logo
