Not able to register com dll.
Please verify details and
http://stackoverflow.com/questions/15344232/not-able-to-register-dll-using-wix-installer
On Mon, Mar 11, 2013 at 2:31 PM, <[email protected]>wrote:
> Send WiX-devs mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wix-devs
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WiX-devs digest..."
>
>
> Today's Topics:
>
> 1. Re: Support for REG_QWORD (64-bit number) (Kariuki, Andrew)
> 2. Re: Support for REG_QWORD (64-bit number) (Rob Mensching)
> 3. WiX 3.8 weekly builds can not be installed on 'clean machine'
> (Boris Dachev)
> 4. Re: WiX 3.8 weekly builds can not be installed on 'clean
> machine' (Rob Mensching)
> 5. Re: WiX 3.8 weekly builds can not be installed on 'clean
> machine' (Boris Dachev)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 11 Mar 2013 13:38:33 -0000
> From: "Kariuki, Andrew" <[email protected]>
> Subject: Re: [WiX-devs] Support for REG_QWORD (64-bit number)
> To: <[email protected]>
> Cc: # IB IT DTACC Wix Support
> <[email protected]>, "Sawyer, Andy"
> <[email protected]>
> Message-ID:
> <
> e81f4a4cfc2e2b4c91b7b192c4eebcea1698d...@elon17p32006a.csfb.cs-group.com>
>
> Content-Type: text/plain; charset=US-ASCII
>
> Hi Rob,
>
> When are you adding support for REG_QWORD Registry Value data type in
> Wix?
>
> We are currently using Wix 3.5, which I believe only has support for:
> String, Integer, Binary, Expandable, and Multistring.
>
> Ref:
> http://msdn.microsoft.com/en-gb/library/windows/desktop/ms724884(v=vs.85
> ).aspx
> http://wix.sourceforge.net/manual-wix2/wix_xsd_registry.htm
>
> Many thanks,
>
> Andrew Kariuki
> App Dev Env - London
> +44 20 7883 8499 (*443 8499)
>
>
>
> ===============================================================================
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
>
> ===============================================================================
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 11 Mar 2013 07:20:06 -0700
> From: Rob Mensching <[email protected]>
> Subject: Re: [WiX-devs] Support for REG_QWORD (64-bit number)
> To: Windows Installer XML toolset developer mailing list
> <[email protected]>
> Cc: # IB IT DTACC Wix Support
> <[email protected]>, "Sawyer, Andy"
> <[email protected]>
> Message-ID:
> <
> cahdhtvebfovcxvic2a3bzsckfvasvbrpjnrq+00cz8qqn+6...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> As soon as the Windows Installer adds support for it.
>
> PS: Why do I have to add everything? <smile/>
>
>
> On Mon, Mar 11, 2013 at 6:38 AM, Kariuki, Andrew <
> [email protected]> wrote:
>
> > Hi Rob,
> >
> > When are you adding support for REG_QWORD Registry Value data type in
> > Wix?
> >
> > We are currently using Wix 3.5, which I believe only has support for:
> > String, Integer, Binary, Expandable, and Multistring.
> >
> > Ref:
> > http://msdn.microsoft.com/en-gb/library/windows/desktop/ms724884(v=vs.85
> > ).aspx
> > http://wix.sourceforge.net/manual-wix2/wix_xsd_registry.htm
> >
> > Many thanks,
> >
> > Andrew Kariuki
> > App Dev Env - London
> > +44 20 7883 8499 (*443 8499)
> >
> >
> >
> >
> ===============================================================================
> > Please access the attached hyperlink for an important electronic
> > communications disclaimer:
> > http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> >
> >
> ===============================================================================
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wix-devs
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Mon, 11 Mar 2013 19:12:06 +0200
> From: Boris Dachev <[email protected]>
> Subject: [WiX-devs] WiX 3.8 weekly builds can not be installed on
> 'clean machine'
> To: Windows Installer XML toolset developer mailing list
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> 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.
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 11 Mar 2013 12:17:43 -0700
> From: Rob Mensching <[email protected]>
> Subject: Re: [WiX-devs] WiX 3.8 weekly builds can not be installed on
> 'clean machine'
> To: Windows Installer XML toolset developer mailing list
> <[email protected]>
> Message-ID:
> <
> cahdhtvd2pgqvgj2glpikgaf6u-sxtrxtij_fq05urshothj...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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 <[email protected]> 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
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wix-devs
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 5
> Date: Mon, 11 Mar 2013 21:31:32 +0200
> From: Boris Dachev <[email protected]>
> Subject: Re: [WiX-devs] WiX 3.8 weekly builds can not be installed on
> 'clean machine'
> To: Windows Installer XML toolset developer mailing list
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 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 <[email protected]
> > <mailto:[email protected]>> 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
> > [email protected] <mailto:
> [email protected]>
> > 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
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/wix-devs
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
> End of WiX-devs Digest, Vol 78, Issue 9
> ***************************************
>
--
*Thanks and Regards,
Shreyas Sali
Software Developer
Mezeo Software
Cell # : 713-315-0041
Skype: shreyassali
***
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
