robocopy equivalent in C#

[=?Utf-8?B?TmlraGlsU2luZ2hhbA==?=]

Hi,
I am building an application that requires copy a decent number of files
around. Till now, to demonstrate the prrof of concept, I used pInvoke to
invoke robocopy to do all the heavy lifting.

Is there any .Net component that I can build/download/buy that will allow me
basic robocopy features such as retry, wait, mirror, file ACL's copy, etc.

Thanks,
Nikhil Singhal

[Nicholas Paldino [.NET/C# MVP]]

Nikhil,

There might be, but it's not included out-of-the box.

You say you are calling the RoboCopy components through the P/Invoke
layer. Why not just continue to call them through the P/Invoke layer?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:C7**********************************@microsof t.com...

Hi,
I am building an application that requires copy a decent number of files
around. Till now, to demonstrate the prrof of concept, I used pInvoke to
invoke robocopy to do all the heavy lifting.

Is there any .Net component that I can build/download/buy that will allow
me
basic robocopy features such as retry, wait, mirror, file ACL's copy, etc.

Thanks,
Nikhil Singhal

[=?Utf-8?B?TmlraGlsU2luZ2hhbA==?=]

I would have loved to continue the use the ribustness of robocopy, but there
are redistribution, packaging issues. Furthermore, requiring the customers to
download something before they can run my app is just not pleasing my bosses.

I would love to hear your other solutions.

Thanks
Nikhil

"Nicholas Paldino [.NET/C# MVP]" wrote:

Nikhil,

There might be, but it's not included out-of-the box.

You say you are calling the RoboCopy components through the P/Invoke
layer. Why not just continue to call them through the P/Invoke layer?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:C7**********************************@microsof t.com...

Hi,
I am building an application that requires copy a decent number of files
around. Till now, to demonstrate the prrof of concept, I used pInvoke to
invoke robocopy to do all the heavy lifting.

Is there any .Net component that I can build/download/buy that will allow
me
basic robocopy features such as retry, wait, mirror, file ACL's copy, etc.

Thanks,
Nikhil Singhal

[Kalpesh]

Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh

[=?Utf-8?B?TmlraGlsU2luZ2hhbA==?=]

Some of the specific features of robocopy that make it interesting are the
1. retry
2. wait
3. mirror
4. copy ACL's

The goal is to remove dependency from robocopy binary. These machines would
be in a production data center and will be tightly locked down.

Thanks
Nikhil

"Kalpesh" wrote:

Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh

[John Timney \(MVP\)]

Well your bosses are wrong if you have to create something you can already
get with no investment.

If your software was going into one of my datacentres I would make sure that
the components needed were delivered and installed, whether there was 1 item
or 1000. Robocopy is one of those trusted components used in datacentres
all over the place and it would simply be added to whatever build approach
was needed. Its simply a pre-requisite.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:86**********************************@microsof t.com...

Some of the specific features of robocopy that make it interesting are the
1. retry
2. wait
3. mirror
4. copy ACL's

The goal is to remove dependency from robocopy binary. These machines
would
be in a production data center and will be tightly locked down.

Thanks
Nikhil

"Kalpesh" wrote:

>Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh

[=?Utf-8?B?TmlraGlsU2luZ2hhbA==?=]

I 100% agree with you John.

Do you know what the re-distribution policy on Robocopy is?
Can I bundle it with my app?

Thanks
Nikhil

"John Timney (MVP)" wrote:

Well your bosses are wrong if you have to create something you can already
get with no investment.

If your software was going into one of my datacentres I would make sure that
the components needed were delivered and installed, whether there was 1 item
or 1000. Robocopy is one of those trusted components used in datacentres
all over the place and it would simply be added to whatever build approach
was needed. Its simply a pre-requisite.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:86**********************************@microsof t.com...

Some of the specific features of robocopy that make it interesting are the
1. retry
2. wait
3. mirror
4. copy ACL's

The goal is to remove dependency from robocopy binary. These machines
would
be in a production data center and will be tightly locked down.

Thanks
Nikhil

"Kalpesh" wrote:

Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh

[John Timney \(MVP\)]

Last time I checked it was in the resource kit. While you can't charge for
it and as long as the user has a valid Windows Server 2003 license you can
include all of Resource Kit tools.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:FB**********************************@microsof t.com...

>I 100% agree with you John.

Do you know what the re-distribution policy on Robocopy is?
Can I bundle it with my app?

Thanks
Nikhil

"John Timney (MVP)" wrote:

>Well your bosses are wrong if you have to create something you can
already
get with no investment.

If your software was going into one of my datacentres I would make sure
that
the components needed were delivered and installed, whether there was 1
item
or 1000. Robocopy is one of those trusted components used in datacentres
all over the place and it would simply be added to whatever build
approach
was needed. Its simply a pre-requisite.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in
message
news:86**********************************@microso ft.com...

Some of the specific features of robocopy that make it interesting are
the
1. retry
2. wait
3. mirror
4. copy ACL's

The goal is to remove dependency from robocopy binary. These machines
would
be in a production data center and will be tightly locked down.

Thanks
Nikhil

"Kalpesh" wrote:

Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh

[=?Utf-8?B?TmlraGlsU2luZ2hhbA==?=]

Most likely, the management "may" decide in future to charge for this tool.

Do you know of any .Net based API's that have similar functionality as
robocopy?

Thanks
Nikhil

"John Timney (MVP)" wrote:

Last time I checked it was in the resource kit. While you can't charge for
it and as long as the user has a valid Windows Server 2003 license you can
include all of Resource Kit tools.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:FB**********************************@microsof t.com...

I 100% agree with you John.

Do you know what the re-distribution policy on Robocopy is?
Can I bundle it with my app?

Thanks
Nikhil

"John Timney (MVP)" wrote:

Well your bosses are wrong if you have to create something you can
already
get with no investment.

If your software was going into one of my datacentres I would make sure
that
the components needed were delivered and installed, whether there was 1
item
or 1000. Robocopy is one of those trusted components used in datacentres
all over the place and it would simply be added to whatever build
approach
was needed. Its simply a pre-requisite.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in
message
news:86**********************************@microsof t.com...
Some of the specific features of robocopy that make it interesting are
the
1. retry
2. wait
3. mirror
4. copy ACL's

The goal is to remove dependency from robocopy binary. These machines
would
be in a production data center and will be tightly locked down.

Thanks
Nikhil

"Kalpesh" wrote:

Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh

[John Timney \(MVP\)]

If they charge for it, they will be in breach of the permitted licence.

I'm not aware of any api functionality to mimic robocopy.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in message
news:18**********************************@microsof t.com...

Most likely, the management "may" decide in future to charge for this
tool.

Do you know of any .Net based API's that have similar functionality as
robocopy?

Thanks
Nikhil

"John Timney (MVP)" wrote:

>Last time I checked it was in the resource kit. While you can't charge
for
it and as long as the user has a valid Windows Server 2003 license you
can
include all of Resource Kit tools.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in
message
news:FB**********************************@microso ft.com...

>I 100% agree with you John.

Do you know what the re-distribution policy on Robocopy is?
Can I bundle it with my app?

Thanks
Nikhil

"John Timney (MVP)" wrote:

Well your bosses are wrong if you have to create something you can
already
get with no investment.

If your software was going into one of my datacentres I would make
sure
that
the components needed were delivered and installed, whether there was
1
item
or 1000. Robocopy is one of those trusted components used in
datacentres
all over the place and it would simply be added to whatever build
approach
was needed. Its simply a pre-requisite.

Regards

John Timney (MVP)
http://www.johntimney.com
http://www.johntimney.com/blog
"NikhilSinghal" <Ni***********@discussions.microsoft.comwrote in
message
news:86**********************************@microso ft.com...
Some of the specific features of robocopy that make it interesting
are
the
1. retry
2. wait
3. mirror
4. copy ACL's

The goal is to remove dependency from robocopy binary. These
machines
would
be in a production data center and will be tightly locked down.

Thanks
Nikhil

"Kalpesh" wrote:

Nikhil,

Out of curiosity, what is it that robocopy does that normal copy
wouldn't do?
I understand that Robocopy is a special purpose solution for file
copying.

Does the normal copying affect things in any way that makes you use
robocopy?
Also, if your network (intranet) is open - you can keep a network
share that has robocopy executables.

You can than call robocopy executable from your .net application.

HTH
Kalpesh