Re: [WiX-users] Fw: Conditional installation of merge modules

2007-11-28 Thread fiordean dacian 

In my case it works (I modified the Directory table if I remember well) and set 
the Default to TARGETDIR some time ago. That installs it correctly but I'm 
having this problem with the reboot on repair, which I want to avoid as I 
invested a lot of time in managing the services (stopping, copying 
configurations, updating dlls, restarting) our app installs just for not 
requesting a reboot, as it is critical for our customers to have a sort of 
'live' update or repair.

Dacian



- Original Message 
From: Simon Dahlbacka <[EMAIL PROTECTED]>
To: fiordean dacian <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: Wednesday, November 28, 2007 4:34:23 PM
Subject: Re: [WiX-users] Fw: Conditional installation of merge modules


FWIW, I was just trying to install the 71 dlls using msm myself the other day 
and never got it to work properly. Then someone on the internet suggested that 
the merge modules were broken and that you just should extract the dlls and 
install them as regular files into your app folder.


So that's what I did. Maybe not that "kosher" but at least it works...

regards,

Simon

On Nov 28, 2007 4:56 PM, fiordean dacian <
[EMAIL PROTECTED]> wrote:





Do you mean installing my app under System folder? Nope.

As for the merge modules, they are installed into their default folder. If I 
have to install the 71 dlls into my app's folder, I need to modify them by hand 
using Orca, right?

Actually MFC71 wasn't a typo, actually I need VC2003 stuff. I just mentioned 
VC2005 runtime since I saw on that blog a discussion about I don't know what 
policy_*.msm thing which btw isn't included with the VC2005 runtime. So forget 
that...


Me either I don't know why this is happenning when repair. I was expecting 
those msm's not to install each time, but rather when not present. It looks 
like they are getting installed no matter. So that's why I was wondering if it's
 possible to condition their installation in Wix.

Thanks,
Dacian


- Original Message 
From: "Wilson, Phil" <
[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net



Sent: Tuesday, November 27, 2007 7:40:53 PM
Subject: Re: [WiX-users] Conditional installation of merge modules





 
 







Are
you installing into the System folder? The 71 Dlls can be side by side, so you
can install them into your application folder.  Visual Studio 2005 support
Dlls are SxS in the WinSxS folder - they're installed differently.  Was
MFC71 a typo? That's the Visual Studio 2003 MFC support, but elsewhere
you're referring to 2005.  I'm not sure what you're
getting at with that "in case of a repair" – this is just at
install time, right? 
 

  
 



Phil
Wilson 
 




  
 





From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
]
On Behalf Of fiordean dacian

Sent: Tuesday, November 27, 2007 7:07 AM

To: wix-users@lists.sourceforge.net

Subject: [WiX-users] Conditional installation of merge modules
 







  
 





Hi,



I'm installing MFC71, CRT and STL merge modules together with my product. The
problem I'm having is Windows Installer asks me to reboot at the end of the
installation in case of a repair since some of those modules are held in use by
Windows Explorer. At the installation, I don't have this problem. I assume is
due to the way those merge modules are made. Is there a way to avoid this?



I'm reading through blogs around Internet about policy_* merge modules (I don't
really understand why do I need all those): 
http://msdn.technetweb3.orcsweb.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx



I downloaded VC 2005 SP1 redistributable package from Microsoft but it doesn't
install anything of that type (ie policy_* merge module files).

http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en




Any thoughts?



Thanks,

Dacian
 







  
 








Be a better pen pal. Text or chat with friends inside Yahoo!
Mail. See
how.
 













  Get easy, one-click access to your favorites. 
 Make Yahoo! your homepage.









  Get easy, one-click access to your favorites. 
 Make Yahoo! your homepage.




-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going

mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___

WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users











  

Get easy, one-click access to your favorites. 
Mak

Re: [WiX-users] Fw: Conditional installation of merge modules

2007-11-28 Thread Simon Dahlbacka 
FWIW, I was just trying to install the 71 dlls using msm myself the other
day and never got it to work properly. Then someone on the internet
suggested that the merge modules were broken and that you just should
extract the dlls and install them as regular files into your app folder.

So that's what I did. Maybe not that "kosher" but at least it works...

regards,

Simon

On Nov 28, 2007 4:56 PM, fiordean dacian <[EMAIL PROTECTED]> wrote:

>
>
>
> Do you mean installing my app under System folder? Nope.
> As for the merge modules, they are installed into their default folder. If
> I have to install the 71 dlls into my app's folder, I need to modify them by
> hand using Orca, right?
>
> Actually MFC71 wasn't a typo, actually I need VC2003 stuff. I just
> mentioned VC2005 runtime since I saw on that blog a discussion about I don't
> know what policy_*.msm thing which btw isn't included with the VC2005
> runtime. So forget that...
>
> Me either I don't know why this is happenning when repair. I was expecting
> those msm's not to install each time, but rather when not present. It looks
> like they are getting installed no matter. So that's why I was wondering if
> it's possible to condition their installation in Wix.
>
> Thanks,
> Dacian
>
>
> - Original Message 
> From: "Wilson, Phil" <[EMAIL PROTECTED]>
> To: wix-users@lists.sourceforge.net
> Sent: Tuesday, November 27, 2007 7:40:53 PM
> Subject: Re: [WiX-users] Conditional installation of merge modules
>
>  Are you installing into the System folder? The 71 Dlls can be side by
> side, so you can install them into your application folder.  Visual Studio
> 2005 support Dlls are SxS in the WinSxS folder - they're installed
> differently.  Was MFC71 a typo? That's the Visual Studio 2003 MFC support,
> but elsewhere you're referring to 2005.  I'm not sure what you're getting at
> with that "in case of a repair" – this is just at install time, right?
>
>
>
> Phil Wilson
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *fiordean dacian
> *Sent:* Tuesday, November 27, 2007 7:07 AM
> *To:* wix-users@lists.sourceforge.net
> *Subject:* [WiX-users] Conditional installation of merge modules
>
>
>
> Hi,
>
> I'm installing MFC71, CRT and STL merge modules together with my product.
> The problem I'm having is Windows Installer asks me to reboot at the end of
> the installation in case of a repair since some of those modules are held in
> use by Windows Explorer. At the installation, I don't have this problem. I
> assume is due to the way those merge modules are made. Is there a way to
> avoid this?
>
> I'm reading through blogs around Internet about policy_* merge modules (I
> don't really understand why do I need all those):
> http://msdn.technetweb3.orcsweb.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx
>
> I downloaded VC 2005 SP1 redistributable package from Microsoft but it
> doesn't install anything of that type (ie policy_* merge module files).
>
> http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en
>
> Any thoughts?
>
> Thanks,
> Dacian
>
>
>  --
>
> Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See
> how. 
>
>
> --
> Get easy, one-click access to your favorites. Make Yahoo! your 
> homepage.
>
>
> --
> Get easy, one-click access to your favorites. Make Yahoo! your 
> homepage.
>
> -
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Fw: Conditional installation of merge modules

2007-11-28 Thread fiordean dacian 




Do you mean installing my app under System folder? Nope.
As for the merge modules, they are installed into their default folder. If I 
have to install the 71 dlls into my app's folder, I need to modify them by hand 
using Orca, right?

Actually MFC71 wasn't a typo, actually I need VC2003 stuff. I just mentioned 
VC2005 runtime since I saw on that blog a discussion about I don't know what 
policy_*.msm thing which btw isn't included with the VC2005 runtime. So forget 
that...

Me either I don't know why this is happenning when repair. I was expecting 
those msm's not to install each time, but rather when not present. It looks 
like they are getting installed no matter. So that's why I was wondering if it's
 possible to condition their installation in Wix.

Thanks,
Dacian


- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Tuesday, November 27, 2007 7:40:53 PM
Subject: Re: [WiX-users] Conditional installation of merge modules





 
 









Are
you installing into the System folder? The 71 Dlls can be side by side, so you
can install them into your application folder.  Visual Studio 2005 support
Dlls are SxS in the WinSxS folder - they’re installed differently.  Was
MFC71 a typo? That’s the Visual Studio 2003 MFC support, but elsewhere
you’re referring to 2005.  I’m not sure what you’re
getting at with that “in case of a repair” – this is just at
install time, right? 
 

  
 



Phil
Wilson 
 




  
 





From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of fiordean dacian

Sent: Tuesday, November 27, 2007 7:07 AM

To: wix-users@lists.sourceforge.net

Subject: [WiX-users] Conditional installation of merge modules
 







  
 





Hi,



I'm installing MFC71, CRT and STL merge modules together with my product. The
problem I'm having is Windows Installer asks me to reboot at the end of the
installation in case of a repair since some of those modules are held in use by
Windows Explorer. At the installation, I don't have this problem. I assume is
due to the way those merge modules are made. Is there a way to avoid this?



I'm reading through blogs around Internet about policy_* merge modules (I don't
really understand why do I need all those): 
http://msdn.technetweb3.orcsweb.com/astebner/archive/2007/02/13/building-an-msi-using-wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx



I downloaded VC 2005 SP1 redistributable package from Microsoft but it doesn't
install anything of that type (ie policy_* merge module files).

http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en



Any thoughts?



Thanks,

Dacian
 







  
 








Be a better pen pal. Text or chat with friends inside Yahoo!
Mail. See
how.
 










  Get easy, one-click access to your favorites. 
 Make Yahoo! your homepage.







  

Get easy, one-click access to your favorites. 
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs -
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users