We're about to release our new WPF application that's based on the .NET 4 framework. I'm trying to see if we can use the client profile rather than the full framework since installing the latter has turned out to take a loooong time (>15-20 minutes post-download)
on our users' computers.
With that said, I've determined that our WPF application has two dependencies that don't exist in the client profile:
- HttpUtility (specifically the UrlEncode() method)
Are there any alternatives to these classes in the client profile that I could use instead?
View Complete Post