Move A directory to its parent (Over a share) does not pass correct information to UserSpace

[GoogleCodeExporter]

What steps will reproduce the problem?
1. MirrorNet
2. Create a share that is not in the root of the mount
3. Connect to share
4. select a child share directory and move to parent in the share

What is the expected output? 
For the Proxy to pass the path of the diretory to be shorter (Higher) than the 
parent
MoveFileProxy replaceIfExisting [0] file: [\Test1\New folder1\ds4] newfile: 
[\Test1\ds4] 

What do you see instead?
The same path being passed in for the source and the target
MoveFileProxy replaceIfExisting [0] file: [\Test1\New folder1\ds4] newfile: 
[\Test1\New folder1\ds4] 

What version of the product are you using? 
0.6.0
On what operating system?
Win 7 x64 Host
Win 7x64 Client or Win XP Client

Please provide any additional information below.
This is probably due to the code that was found in issue 238 where it forcible 
copies the name of the source over the target dir

Original issue reported on code.google.com by smurf...@gmail.com on 20 Nov 2011 at 7:53

[GoogleCodeExporter]

Added to http://liquesce.codeplex.com/workitem/9855

Original comment by smurf...@gmail.com on 20 Nov 2011 at 7:56

[GoogleCodeExporter]

This is not as bad as it sounds..
The above is only present when dropping files from higher up onto the root of 
the share.
I.e. if 
The Share is at \\Test1
And the Source is \\Test\New\dir
and the intended target is \\Test\dir
Then Dokan would pass source=\\Test\New\dir   target=\\Test\New\dir
BUT
if we have source=\\Test\New\dir\fred
target = \\Test\New\fred
then dokan will pass the following incorrect information
MoveFileProxy replaceIfExisting [0] file: [\Test1\New folder1\ds4\TestDir] 
newfile: [\Test1\New folder1\ds4\New folder1\TestDir] 
Which means the workaround I did for the MoveFile (Dokan issue 238) will kick 
in and correct it. Yay

Original comment by smurf...@gmail.com on 20 Nov 2011 at 8:19