File.Move not working as expected

[Danny]

Hello,

I was hoping someone might be able to shed some light on this bizarre
behaviour.

I have observed some strange behaviour with System.IO.FIle.Move where it
seems to be copying a file as opposed to actually moving it. The following is
a description of my setup:

Two separate machines (A and B) both running Windows Server 2003. Machines
reside on the same domain.

An application is running on machine A and it is responsible for managing
files on machine B. In particular it will (among other things) be moving a
file from one share (share1) on machine B to another share (share2) on
machine B.

Using an example, we have a file called bla.bla that is currently sitting in
location share1. The call in the application on machine A will attempt to
move bla.bla to location share2. e.g.

File.Move(share1/bla.bla, share2/bla.bla)

This call blocks until the operation is complete however upon return rather
then seeing that bla.bla has been moved, we actually see it now exists in
both locations (share1 *AND* share2). It SHOULD only now reside in share2.

The files in question can range in size from aprox. 10MB to say 300MB

Can anyone explain this wierdness? As far as I know, it should not be
happening.

Best regards,

Danny

[Eddie de Bear]

Maybe it has to do with shares in particular... A move operation may not be
supported by all client types, and therefore the only "common" way of moving
a file (over network shares) is by copying and deleting?? Just a guess...

"Danny" wrote:

Hello,

I was hoping someone might be able to shed some light on this bizarre
behaviour.

I have observed some strange behaviour with System.IO.FIle.Move where it
seems to be copying a file as opposed to actually moving it. The following is
a description of my setup:

Two separate machines (A and B) both running Windows Server 2003. Machines
reside on the same domain.

An application is running on machine A and it is responsible for managing
files on machine B. In particular it will (among other things) be moving a
file from one share (share1) on machine B to another share (share2) on
machine B.

Using an example, we have a file called bla.bla that is currently sitting in
location share1. The call in the application on machine A will attempt to
move bla.bla to location share2. e.g.

File.Move(share1/bla.bla, share2/bla.bla)

This call blocks until the operation is complete however upon return rather
then seeing that bla.bla has been moved, we actually see it now exists in
both locations (share1 *AND* share2). It SHOULD only now reside in share2.

The files in question can range in size from aprox. 10MB to say 300MB

Can anyone explain this wierdness? As far as I know, it should not be
happening.

Best regards,

Danny