Re: [WiX-users] detecting .net 2.0

2007-10-25 Thread Matt Hoover (VSNC)
It is not possible to have only .Net 3.0 or only .Net 3.5.  .Net 3.0 builds 
upon and extends .Net 2.0, and if .Net 2.0 isn't installed when you install 
.Net 3.0, it will install .Net 2.0 for you.  And .Net 3.5 builds upon and 
extends .Net 3.0, so it will also install and/or patch .Net 2.0 and .Net 3.0 
during the .Net 3.5 install.
--matt hoover

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy
Sent: Thursday, October 25, 2007 4:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] detecting .net 2.0


I found this post - which is very helpful: 
http://blogs.msdn.com/robmen/archive/2006/10/17/wix-v3-syntax-for-detecting-the-clr.aspx

However, I've read that .NET 2.0 applications will work with .NET 2.0, .NET 
3.0, or .NET 3.5 installed (as they all use the same core CLR 2.0).

Is the NETFRAMEWORK20 variable defined for machines that have ONLY .NET 3.0, or 
ONLY .NET 3.5?

If not, what's the recommended best practice for requiring anything that can 
run 2.0 code, in other words, .NET 2.0 or higher?

Thanks,
Kelly Leahy
Milliman, Inc.

**
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful.  Unless indicated
to the contrary: it does not constitute professional advice or
opinions upon which reliance may be made by the addressee or any
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries
guidelines.
**
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] detecting .net 2.0

2007-10-25 Thread Kelly Leahy
Thanks Matt.

That was the critical piece of information I was missing.  So is the .NET 
3.0 installation actually a bootstrapper that installs the .NET 2.0 
installation via delegation to the original .NET 2.0 package, or are the 
installs combined?

I guess the answer doesn't really matter, but I'm just curious.

Kelly




Matt Hoover (VSNC) [EMAIL PROTECTED]

10/25/2007 03:37 PM

To
Kelly Leahy [EMAIL PROTECTED], wix-users@lists.sourceforge.net 
wix-users@lists.sourceforge.net
cc

Subject
RE: [WiX-users] detecting .net 2.0






It is not possible to have only .Net 3.0 or only .Net 3.5.  .Net 3.0 
builds upon and extends .Net 2.0, and if .Net 2.0 isn’t installed when you 
install .Net 3.0, it will install .Net 2.0 for you.  And .Net 3.5 builds 
upon and extends .Net 3.0, so it will also install and/or patch .Net 2.0 
and .Net 3.0 during the .Net 3.5 install.
--matt hoover
 
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy
Sent: Thursday, October 25, 2007 4:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] detecting .net 2.0
 

I found this post - which is very helpful: 
http://blogs.msdn.com/robmen/archive/2006/10/17/wix-v3-syntax-for-detecting-the-clr.aspx
 


However, I've read that .NET 2.0 applications will work with .NET 2.0, 
.NET 3.0, or .NET 3.5 installed (as they all use the same core CLR 2.0). 

Is the NETFRAMEWORK20 variable defined for machines that have ONLY .NET 
3.0, or ONLY .NET 3.5? 

If not, what's the recommended best practice for requiring anything that 
can run 2.0 code, in other words, .NET 2.0 or higher? 

Thanks, 
Kelly Leahy 
Milliman, Inc. 

**
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure, 
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful.  Unless indicated
to the contrary: it does not constitute professional advice or 
opinions upon which reliance may be made by the addressee or any 
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries 
guidelines.
**



**
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure, 
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful.  Unless indicated
to the contrary: it does not constitute professional advice or 
opinions upon which reliance may be made by the addressee or any 
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries 
guidelines.
**
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] detecting .net 2.0

2007-10-25 Thread Matt Hoover (VSNC)
I don’t remember the exact mechanics, but the later installers do bootstrap the 
earlier installers and service packs.  I am forgetting right now where .Net 2.0 
SP1 was introduced, but by the time .Net 3.5 is installed, .Net 2.0 will be 
patched to the SP1 level.  Without looking at the installers, I can’t remember 
what is done in what order, but the effect is to have the latest service packs 
for .Net 2.0 and .Net 3.0 installed by the time that .Net 3.5 completes its 
install.  If you have a Visual Studio 2008 Beta 2 install disk, you can look at 
the installers that do this.  If you look in the WCU\dotNetFramework on the 
disk, you can see the installers that are used.
--matt hoover

From: Kelly Leahy [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 6:40 PM
To: Matt Hoover (VSNC)
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] detecting .net 2.0


Thanks Matt.

That was the critical piece of information I was missing.  So is the .NET 3.0 
installation actually a bootstrapper that installs the .NET 2.0 installation 
via delegation to the original .NET 2.0 package, or are the installs combined?

I guess the answer doesn't really matter, but I'm just curious.

Kelly


Matt Hoover (VSNC) [EMAIL PROTECTED]

10/25/2007 03:37 PM

To

Kelly Leahy [EMAIL PROTECTED], wix-users@lists.sourceforge.net 
wix-users@lists.sourceforge.net

cc

Subject

RE: [WiX-users] detecting .net 2.0







It is not possible to have only .Net 3.0 or only .Net 3.5.  .Net 3.0 builds 
upon and extends .Net 2.0, and if .Net 2.0 isn’t installed when you install 
.Net 3.0, it will install .Net 2.0 for you.  And .Net 3.5 builds upon and 
extends .Net 3.0, so it will also install and/or patch .Net 2.0 and .Net 3.0 
during the .Net 3.5 install.
--matt hoover

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy
Sent: Thursday, October 25, 2007 4:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] detecting .net 2.0


I found this post - which is very helpful: 
http://blogs.msdn.com/robmen/archive/2006/10/17/wix-v3-syntax-for-detecting-the-clr.aspx

However, I've read that .NET 2.0 applications will work with .NET 2.0, .NET 
3.0, or .NET 3.5 installed (as they all use the same core CLR 2.0).

Is the NETFRAMEWORK20 variable defined for machines that have ONLY .NET 3.0, or 
ONLY .NET 3.5?

If not, what's the recommended best practice for requiring anything that can 
run 2.0 code, in other words, .NET 2.0 or higher?

Thanks,
Kelly Leahy
Milliman, Inc.

**
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful.  Unless indicated
to the contrary: it does not constitute professional advice or
opinions upon which reliance may be made by the addressee or any
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries
guidelines.
**


**
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful.  Unless indicated
to the contrary: it does not constitute professional advice or
opinions upon which reliance may be made by the addressee or any
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries
guidelines.
**
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now  http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users