What happoned to System.Uri(string, bool)?? [modified]
-
I've not used URI's a lot of late, but I just noticed that telling the Uri constructor:
System.Uri(string uriString, bool dontEscape)
in .NET 2.0 to not escape the string is depicted AND the function isn't even included in the framework > 2.0) MSDN says to just useUri(string uriString)
If you use that how the heck can you send something to "mypage.html?view=2.0" if it escapes all strings entered?
-Spacix All your skynet questions[^] belong to solved
modified on Friday, April 18, 2008 2:45 PM
-
I've not used URI's a lot of late, but I just noticed that telling the Uri constructor:
System.Uri(string uriString, bool dontEscape)
in .NET 2.0 to not escape the string is depicted AND the function isn't even included in the framework > 2.0) MSDN says to just useUri(string uriString)
If you use that how the heck can you send something to "mypage.html?view=2.0" if it escapes all strings entered?
-Spacix All your skynet questions[^] belong to solved
modified on Friday, April 18, 2008 2:45 PM
Wow, never thought I'd see something this dumb, done by the .NET team... I found the solution: You have to make Two URI's and use one as the base URI, so now you have two strings (for no reason), more than one line of code, and two URI objects... example:
Uri base = new Uri("http://www.google.com/search");
Uri final = new Uri (base, "q=WTF");Which is sooo much easier and better than: :rolleyes: :rolleyes: :rolleyes:
Uri final = new Uri ("http://www.google.com/search?q=WTF", true);
WTF! why on earth would a programmer willing change it TO this?? This belongs on http://www.thedailywtf.com not in .NET :(
-Spacix All your skynet questions[^] belong to solved