Signing is not new. None of this is new.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, January 08, 2009 22:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
But I thought signing was
olset.
Subject: Re: [WiX-users] Building signed WiX Source
Yep. This need has never come up in the 4.5 years WiX has existed
externally.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, January 08, 2009 22:14
To: General discussion for Windows Installe
ssume I must be alone in needing this otherwise it would have come up
before.
Neil
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: 08 January 2009 21:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX
ust be alone in needing this otherwise it would have come up
before.
Neil
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: 08 January 2009 21:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
ML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
That was it, thank you very much. I will be documenting the things I
find on my blog but will also try to update the WiX help file in the
near future.
I will also see if there is some way to automate this.
Neil
-Original Message
]
Sent: 08 January 2009 18:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
In src\Votive\sconce\Properties\AssemblyInfo.cs you'll see the key
tokens for the last couple keys we've used. You'll need your own in
there t
Neil Sleightholm wrote:
> Do you mean copy the hint paths from the 2008 project? The 2005 project
> doesn't have any hint paths in it.
>
I'm wondering whether without the hint paths, it's picking up wrong
versions. But I think the InternalsVisibleTo fix is the right one.
--
sig://boB
http:/
mailto:n...@x2systems.com]
Sent: Thursday, January 08, 2009 09:51
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
I am not sure I follow, I can't use the same key that is yours and you
don't ship the private part (quite corre
Neil Sleightholm wrote:
> I am not sure I follow, I can't use the same key that is yours and you
> don't ship the private part (quite correctly) and if you use the public
> key you can't run the code.
>
src\Votive\sconce\Properties\AssemblyInfo.cs has InternalsVisibleTo for
votive*.dll with t
p.
-Original Message-
From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com]
Sent: Thursday, January 08, 2009 00:24
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
from the error message, a plausible explanation is the key used is
rom: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com]
Sent: Thursday, January 08, 2009 00:24
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
from the error message, a plausible explanation is the key used is one
that is used is also
ent: Thu 08/01/2009 04:12
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
Rob Mensching wrote:
> I don't know. Works on the build machine today.
>
I ran into this about a year ago. Take a look at the votive2008.csproj
ed
> n...@x2systems.com <mailto:n...@x2systems.com>
>
>
>
>
> From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
> Sent: Wed 07/01/2009 23:14
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users]
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Wed 07/01/2009 23:14
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Sour
Rob Mensching wrote:
> I don't know. Works on the build machine today.
>
I ran into this about a year ago. Take a look at the votive2008.csproj
HintPath metadata for all the VSSDK assemblies. If you create the same
directory structure, I believe everything will work.
--
sig://boB
http://
I don't know. Works on the build machine today.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, January 07, 2009 15:00
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
I have
ssage-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: 07 January 2009 22:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
2005 and 2008 both. I think that's a 2008 thing but I'm not sure if
that fixes the 2
or Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
If I build without setting OFFICIAL_WIX_BUILD everything is ok, it is
only a problem when I try to sign it.
Is "VSIP SDK" == "Visual Studio 2005 SDK Version 4."
Neil
-Original Me
09 22:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
Do you have the VSIP SDK? I *think* that's what is required. There is
a fair bit of software that has to be installed when doing an official
build.
-Original Message---
n for Windows Installer XML toolset.
Subject: [WiX-users] Building signed WiX Source
I want to be able to build the WiX source to run on machines other than
the build machine. By default the build processes delay signs the code
with the public WiX key and so it won't run unless you trust the
I want to be able to build the WiX source to run on machines other than
the build machine. By default the build processes delay signs the code
with the public WiX key and so it won't run unless you trust the public
key. Looking at the build code it seems the answer to this is to create
my own publi
21 matches
Mail list logo
