Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > .net 3.51
 

.net 3.51

A am working on an install and tested it on a clean Vista 64 with SP1 and found I needed .NET 3.51. Is .NET 3.51 included in SP2 and when was SP2 released?

Does anyone know what the chances of finding a machine without .NET 3.51 on are? The product is small enough that we are shipping withthe install on a mini cd, which does not leave enough room to include .net 3.51. My fall back position is the user must have internet access.
BarberColman  Friday, September 04, 2009 7:46 PM
There is no such thing as .Net 3.51. There is .Net 3.5 SP-1, is that what you are talking about?

Windows Vista was shipped with .Net 3.0, so it won't have .Net 3.5 Sp-1 inherently. However, Microsoft IS pushing .Net 3.5 SP-1 to any machine with any version of .Net on it via Windows Updates as a critical update, so more people have it than not.

You should check into the Client Framework and see if that will work for your application. This is a subset of .Net 3.5 that only includes the parts needed for a client application -- basically it's .Net w/o the web bits. I think it's about 20MB.

But I think if you use that, your clients will still need Internet access. How it works is if they don't have any version of .Net installed, it will install the Client Framework. If they have ANY version of the .Net Framework installed, it will try to go out to the internet and upgrade the user to .Net 3.5.

Can you use regular CD's instead of a miniCD? It seems like that would fix your problem.

RobinDotNet
Click here to visit my ClickOnce blog!
RobinDotNet  Saturday, September 05, 2009 5:09 PM
There is no such thing as .Net 3.51. There is .Net 3.5 SP-1, is that what you are talking about?

Windows Vista was shipped with .Net 3.0, so it won't have .Net 3.5 Sp-1 inherently. However, Microsoft IS pushing .Net 3.5 SP-1 to any machine with any version of .Net on it via Windows Updates as a critical update, so more people have it than not.

You should check into the Client Framework and see if that will work for your application. This is a subset of .Net 3.5 that only includes the parts needed for a client application -- basically it's .Net w/o the web bits. I think it's about 20MB.

But I think if you use that, your clients will still need Internet access. How it works is if they don't have any version of .Net installed, it will install the Client Framework. If they have ANY version of the .Net Framework installed, it will try to go out to the internet and upgrade the user to .Net 3.5.

Can you use regular CD's instead of a miniCD? It seems like that would fix your problem.

RobinDotNet
Click here to visit my ClickOnce blog!
RobinDotNet  Saturday, September 05, 2009 5:09 PM

You can use google to search for other answers

Custom Search

More Threads

• Can not turn off automatic update
• ClickOnce app migrations
• Programatically set the TARGETDIR
• Question about file extensions
• MSI Issue - ReInstall app for every login User
• ClickOnce + ""'xxxx' does not refer to a page or folder in this web. (Visual Studio Team System 2005)
• HELP! Problem with Installation .NET Framework 2.0 on Windows 2003 SP1
• How to make single execution file
• DSOFramer deployment
• Bootstrapping .Net framework 3.5 from VS2005