>My point was that, regardless of how you deploy, the web.config produced by VS is heavily dependent on the Target Framework selected for it's project. As an example try 'downgrading' a .NET 4.0 web project to .NET 3.5. and compare web.config before and after. Modifying the .net target settings directly in the web.config on a production server where DLLs have been compiled using a different version seems inherently risky.....

Yes, that's right. Since last night, we no longer have this attribute in any web.confg.

Thanks