index > ClickOnce and Setup & Deployment Projects > VS 2008 SP1, Click Once, Prerequisites, Client Profile option + 3.5 SP 1 option

VS 2008 SP1, Click Once, Prerequisites, Client Profile option + 3.5 SP 1 option

I am producing a ClickOnce (WCF Client) application that will be installed by consumers. Most but not all consumers will have XP SP2+. Some Vista, some even Vista 64 (like me at home). I have no information about whether or not .Net is installed on the consumer's system.

Because the application is based on .Net 35 SP1, that option is marked as a prerequisite and has been QA'ed as such. If it is possible, i would like to reduce the size of the installation for as many users as possible. The Visual Studio 2008 SP1 - Prerequisites DIALOG shows [X].Net Framework 3.5 SP1, and [ ] .Net Framework Client Profile. Do i leave them both checked and publish, or only the .Net Client Profile option checked?

Thank you very much for your time and any assistance.

m6rk Friday, July 24, 2009 11:22 AM

You only need the .NET Client Profile checked. Also, be sure that your application has the "Client-only Framework subset" checkbox enabled (on the "Application" tab in project properties).

-Jennifer

Marked As Answer bym6rk Friday, July 24, 2009 7:58 PM

jenlouie Friday, July 24, 2009 7:42 PM

You only need the .NET Client Profile checked. Also, be sure that your application has the "Client-only Framework subset" checkbox enabled (on the "Application" tab in project properties).

-Jennifer

Marked As Answer bym6rk Friday, July 24, 2009 7:58 PM

jenlouie Friday, July 24, 2009 7:42 PM

Thank you!

m6rk Friday, July 24, 2009 7:59 PM

But there IS something you need to know about the Client Framework. If your user has NO version of the .Net Framework installed, it will only install the Client Framework, which is about 20MB.

If your user has ANY previous version of the .Net Framework installed (other than 3.5), it will install the whole thing.

Another piece of info that might help you is that Microsoft is deploying the .Net 3.5 Framework in Windows Update, and *has* been since February. So any machine that is accepting updates and has ANY version of .Net on it will be updated by Microsoft to 3.5if it hasn't already been.

So pushing the client framework is a great idea. You end up pushing that as a prerequisite, and if the user has no .Net, it installs the Client Framework, and if they have windows updates enabled, Microsoft comes along behind you and installs the whole shebang.

RobinDotNet

Click here to visit my ClickOnce blog!

RobinDotNet Wednesday, July 29, 2009 9:47 AM

I configured my ClickOnce application (which checks for new version each startup) for Client Profile Framework + .Net Framework Client Profile and I perceive that it takes slightly longer to launch. Am I nuts or does using the Client-only Framework subset + .Net Framework Client Profile prerequisite cause a lag in the start of the application?

m6rk Tuesday, August 04, 2009 1:15 PM

When you say "the start of the application", do you mean when it is installing the prerequisites, or after the application is installed and they are double-clicking on the shortcut to run the application? How much of a lag are you seeing?

When you run the app via the shortcut, it doesn't even check the prerequisites, so if that's the case, there wouldn't be any impact.

If you are running it by double-clicking on setup.exe (or clicking Install on the publish page, which runs setup.exe), it might take a second longer, but I can't imagine it taking that much longer, because it's just a matter of the installation checking the registry to see what version of .Net installed.

RobinDotNet

Click here to visit my ClickOnce blog!

RobinDotNet Monday, August 10, 2009 5:44 AM

You can use google to search for other answers

Custom Search

More Threads

• Installer running automatically when Click shortcut of application

• VS 2005 Setup Project- Display files during installation

• How to link a WiX library in DSL Setup Project

• Desktop Shortcut Runs Installer

• Including .NET Install In Setup Project

• How to launch ClickOnce application programmatically

• Setup file creation - Warnings

• Registry Permissions

• MSI with custom action(created vai vs2003) insatll hang on vista

• Publish Application Files