+6  A: 

Visual Studio 2008 SP1 adds support for the "Client Profile" subset of the .NET Framework. If the Windows XP SP3 machines you're targeting don't have any version of the .NET Framework installed already, this will install a slimmed-down version of the Framework with the assemblies you need for a WPF app. Microsoft provides a bootstrapper installer that will install/update the .NET Framework on the client machine, then chain to your installer to install your application. Here are some links to get started:

Bradley Grainger
The client profile is almost exactly useless for anyone who shipped a .net 2 app, because you have to ship all 250M of .net 3[.5] for your existing customers. From where I sit, it's a solution to a problem which is almost the one I have, but doesn't help me at all.
James Ogden
Yes, I can't imagine that it'll be too useful in practice until .NET 4.0 ships. Then (because virtually no one will have it installed already), the Client Profile should make installation a lot slimmer.
Bradley Grainger
I was successful when using this approach, however, is there a way to make the application appear on the start -> programs menu?
Carlo
A: 

When you use ClickOnce, In your Deploy Option from Project Propertys, set your requireds assemblyes as included, then if you really needs some assemblyes, use gacutil.exe or drag and drop on your client local GAC

Angel Escobedo