Is it possible to deploy a .NET 4.0 to a machine with only .NET 3.5 SP1 installed?-Collection of common programming errors

I am working on a WPF application that requires .NET 4.0 to run. The machines on the enterprise are all running .NET 3.5 SP1. Is it possible to deploy the application with its .NET 4 DLLs without having to install the full .NET 4 Framework on the client machines?

There are two parts of our implementation marries us to .NET 4.0

  1. The use of the Data Grid user control (this is the easiest issue to overcome).
  2. The use of the enableUnsecuredResponse property for my WCF binding.

  
    
      
      
        
      
      
    
  

Microsoft has release the following Hot Fix: A hotfix that enables WCF to send secured messages and to receive unsecured responses, and to send unsecured messages and to receive secured responses, is available for the .NET Framework 3.5 SP1 but if I am to deploy this Hot Fix to the enterprise, I might as well do that for the .NET 4.0 Client Profile and resolve all my issues then and there.

I am aware of the .NET 4.0 Client Profile installation. What I’m trying to avoid is the need to push out the installation of the framework for just my application.

My Current Thought: It can’t be done. Even if I deploy the .NET 4 DLLs that are referenced, they will still try to be handled by an older version of the CLR which won’t be able to understand them.