Using the Client Profile, is it possible to reference an assembly that references System.Web?

Question

I'm creating a small application that requires an assembly that also requires the System.Web assembly. The classes I am using from the referenced assembly do not require System.Web.

I would like the application to target the 4.0 client profile, which means System.Web is not available.

Is it possible to convince Visual Studio to reference the assembly and compile? It's my understanding that the System.Web assembly wouldn't be loaded at run-time, unless it was needed.

Is there some MSBuild trick, or an attribute I can add to the client profile compliant classes that would get VS to compile?