I have two Uri objects passed into some code, one is a directory and the other is a filename (or a relative path)
var a = new Uri("file:///C:/Some/Dirs");
var b = new Uri("some.file");
when I try and combine them like this:
var c = new Uri(a,b);
I get
file:///C:/Some/some.file
where I wold expect to get the same effect as with Path.Combine
(as that is the old code I need to replace):
file:///C:/Some/Dirs/some.file
I can't think of a clean solution to this.
The ugly solution being to add a /
to the Uri if it's not there
string s = a.OriginalString;
if(s[s.Length-1] != '/')
a = new Uri(s + "/");
Well, you're going to have to tell the Uri somehow that the last part is a directory rather than a file. Using a trailing slash seems to be the most obvious way to me.
Bear in mind that for many Uris, the answer you've got is exactly right. For example, if your web browser is rendering
and it sees a relatively link of "other.html" it then goes to
not
Using a trailing slash on "directory" Uris is a pretty familiar way of suggesting that relative Uris should just append instead of replacing.
Why not just inherit from Uri and use that, ie. do in constructor what you need to do to fix it up? Refactoring is cheap assuming this is internal to assembly or within reach..
You can try this extension method! Works always! ;-)
Angelo, Alessandro
This should do the trick for you:
This constructor follow the standard relative URI rules so the
/
are important :http://example.net
+foo
=http://example.net/foo
http://example.net/foo/bar
+baz
=http://example.net/foo/baz
http://example.net/foo/
+bar
=http://example.net/foo/bar
http://example.net/foo
+bar
=http://example.net/bar
http://example.net/foo/bar/
+/baz
=http://example.net/baz
add a slash end of your first uri, URI will ignore more than one slash (/)
EDIT: