In the .NET 3.5 timeframe and earlier, many client developers referenced System.Web.dll in order to be able to use System.Web.HttpUtility and its helpful encode/decode and parse methods. While those functions were really useful, the full framework is a pretty hefty tax to pay for just a couple methods. I ran across this tax today when I tried to use a popular twitter library (written in .NET 3.5) with a .NET 4 client profile project. That project references the full System.Web.dll and won't compile under a client profile project in .NET 4. You no longer need to rely on ASP.NET DLLs on the client just to encode/decode HTML. The .NET 4 client profile includes a new class that provides some of the functionality of System.Web.HttpUtility, without...(read more) ...
Go to the complete details ...