Design Guideline Update: Uri vs. string

re: Design Guideline Update: Uri vs. string

Andy — Tue, 13 Jan 2004 00:24:00 GMT

Any chance the "excellent" doc can be put somewhere public?

re: Design Guideline Update: Uri vs. string

Brad Abrans — Tue, 13 Jan 2004 01:16:00 GMT

Sorry about the bad whitepaper link... I am working on getting it posted outside the farm now..

re: Design Guideline Update: Uri vs. string

Ken Brubaker — Fri, 16 Jan 2004 21:08:00 GMT

Can you make a more generic rule for when to use composite types and simple types. This rule could apply for System.Guid and string for example.

New and Notable 35

Sam Gentile's Blog — Sun, 18 Jan 2004 19:32:00 GMT

re: Design Guideline Update: Uri vs. string

Peter — Mon, 19 Jan 2004 20:21:00 GMT

I'm not so happy with the uri class because:

I’ve noticed some strange behaviors with the uri class,
First the constructor has strange behavior (first code snippet)
Second the EQUALS method and the ==/!= operators behave differently ?

string partialUrl="../../Styles/Common/Styles.css";
string anotherUrl="../Styles/Common/Styles.css";
Uri remoteUri = new Uri("http://pdemeyer01/nbbcms/test.html");
Uri anUri = new Uri(remoteUri,partialUrl);
Console.WriteLine(anUri.AbsoluteUri); //prints http://pdemeyer01/../Styles/Common/Styles.css INCORRECT
anUri = new Uri(remoteUri,anotherUrl );
Console.WriteLine(anUri.AbsoluteUri); //prints http://pdemeyer01/Styles/Common/Styles.css CORRECT

Queue aQueue = new Queue();
Uri NL =new Uri("http://localhost/NBBCMS/WebForm1.aspx?Language=NL");
Uri UK=new Uri("http://localhost/NBBCMS/WebForm1.aspx?Language=UK");

aQueue.Enqueue(NL);
if (!aQueue.Contains(UK))
Console.WriteLine("UK Not in the queue");
else
Console.WriteLine("UK Already in Queue"); //prints UK Already in Queue INCORRECT
if (UK.Equals(NL))
Console.WriteLine("UK Equals NL"); //prints UK Equals NL INCORRECT
if (UK!=NL)
Console.WriteLine("UK != NL"); //prints UK != NL CORRECT

re: Design Guideline Update: Uri vs. string

Brad Abrams — Tue, 20 Jan 2004 04:55:00 GMT

From the dev team: You will be glad to know that we have fixed this in the current builds...

Now it prints:

http://pdemeyer01/Styles/Common/Styles.css">http://pdemeyer01/Styles/Common/Styles.css
http://pdemeyer01/Styles/Common/Styles.css">http://pdemeyer01/Styles/Common/Styles.css

UK Not in the queue

UK != NL

Note Uri.Equals() will still ignore userinfo and fragment parts.

For now this is to maintain compatibility with v1.0 when a uri is used to resolve a resource (not to identify it)

Ignoring a query part was just a plain bug.

Microsoft Design Guidelines

James Geurts' Blog — Mon, 01 Mar 2004 20:34:00 GMT

re: Design Guideline Update: Uri vs. string

Doug McClean — Mon, 17 May 2004 14:57:00 GMT

This is off topic, but does anyone have any idea why System.Uri inherits System.MarshalByRefObject? Seems like a very odd choice for such an obviously serializable type, that is marked as serializable, and that appears to be immutable (doesn't have any set accessors or methods that seem like they should have side effects). Can anyone weigh in on this? Under what circumstances would a serializable type be marshaled by reference, anyway?

System.Uri and MarshalByRefObject

Brad Abrams — Wed, 28 Jul 2004 06:14:00 GMT