Ahh, yes, VS2012 support for WinXP. Need to get that enabled on the build
machine. <sigh/> Would be great if you could open a bug to track the issue.
Thanks.
On Mon, Mar 11, 2013 at 12:31 PM, Boris Dachev <bdac...@gmail.com> wrote:
> Sorry my mistake!
> It all started that I was unable to install 3.8 on clean XP (neither
> weekly build nor my local). My investigation was done for my local build
> and hence the result in my previous email.
>
> But I found later that with weekly builds of 3.8 there is another issue
> with XP. These builds are done with VS2012 and targeting minimum OS 6.0
> which prevents them from installing on XP. I believe that is more serious
> problem as it is not possible to create a setup targeting XP.
>
> I was about to write another thread on that issue but was still doing some
> tests.
> B.
>
>
>
> On 3/11/2013 9:17 PM, Rob Mensching wrote:
>
> Weekly builds should be correctly strong name signed. We'd be having a
> lot of people scream if that wasn't working, I would think. <smile/>
>
> Local builds are intended to be used locally and fixes published to a
> future weekly build. So, those you need to add the exclusions, by design.
>
>
> On Mon, Mar 11, 2013 at 10:12 AM, Boris Dachev <bdac...@gmail.com> wrote:
>
>> Hi Guys,
>>
>> I met a problem that both weekly builds and my local builds can not be
>> installed on 'clean machine'.
>> Digging into the problem I found that the reason is that the assemblies
>> are not signed.
>> Is there easy way to overcome that problem apart from adding exclusions
>> via sn.exe tool?
>>
>> Best regards,
>> Boris.
>>
>> PS: Sorry if I am not first one asking about that but was unable to find
>> anything in archive.
>>
>>
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>> endpoint security space. For insight on selecting the right partner to
>> tackle endpoint security challenges, access the full report.
>> http://p.sf.net/sfu/symantec-dev2dev
>> _______________________________________________
>> WiX-devs mailing list
>> WiX-devs@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-devs
>>
>>
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
>
>
>
> _______________________________________________
> WiX-devs mailing
> listWiX-devs@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
