After the April 2007 Windows Update to the .Net framework 2.0, the System.URI which accepts a string constructor will not remove erroneous forward slashes.
This was unintentional behavior.
https://connect.microsoft.com/Visual...dbackID=288395
I have not tested myself whether this also affects the UriBuilder class.
My discovery of this happened with a client executable which kept receiving 500 server errors from a remote server it was trying to connect to.
