views:

1291

answers:

3

I just started using the WPF WebBrowser that is included in Net 3.5 SP1. I built my setup project (which I have been using prior to moving to 3.5 SP1) and installed it on a test machine but the WebBrowser was not available.

What must I do to be sure that the setup.exe/msi combination checks for and installs SP1?

A: 

On my way to answering my own question. Double-clicking on the Microsoft .net Framework in the Detected dependencies one can choose the version.

Now the question is which is appropriate, 3.5.30729 or 3.5 SP1 Client?

EDIT: 3.5.30729 works. Any ideas of the difference between the two?

EDIT: Double-clicking on the .net Framework above shows .NET Framework as a Launch condition. This is where I changed the version. (I'd add a screenshot, but I don't have one at a URL, only on my desktop.

rathkopf
Client more than likely means Client Profile, i.e. the subset of the framework that doesnt have e.g. ASP.NET
Ruben Bartelink
NB If 3.5 is installed, doesnt warn you need 3.5, see http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/698a0f78-1808-45f1-a615-f3acec50a84d/ and http://stackoverflow.com/questions/245913/delivery-of-net-3-5-sp1
Ruben Bartelink
+2  A: 
Jason Stevenson
also should mention the launch condition and the fact that the check is for 3.5, not SP1 so 3.5 owners will not be auto forced to upgrade to SP1
Ruben Bartelink
when I say the check, I refer to the launch condition which is triggered when you run the MSI [directly, not via the bootstrapper].
Ruben Bartelink
A: 

In the setup project, add some launch conditions. This page shows you how exactly: http://jelle.druyts.net/2005/04/09/CheckingForNET11ServicePack1InAnMSI.aspx

That checks for a SP1, but what about when 4.0 is installed and you're happy with that instead of 3.5SP1 ? (BTW amended reg paths at http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/698a0f78-1808-45f1-a615-f3acec50a84d/)
Ruben Bartelink