"VBoxManage guestcontrol copyto" issues

[BuG]

This feature seems to be in early beta state, I hope you will check the whole code again. I don't know if the responsible developer tested it at all.

After you fixed this one in the final but you didn't fix this one, I have a new "single character file/directory name" problem.

E.g. if I want to copy a file c:\test\a ("a" is a file name) the copyto command creates a new file c:\test\aa on the VM.
The other problem appears if "a" is a directory name. When I want to do a recursive copy of the directory c:\test\a with the files c:\test\a\test.txt and c:\test\a\whatever.txt then I get c:\test\atest.txt and c:\test\awhatever.txt on the VM. That's not really funny...

[Sasquatch]

Check the Bugtracker (separate account needed) and add your comment to the ticket if one exists for your linked issue, else create a new one and address both problems.

[abcuser]

BuG, as achimha has written: "The responsible engineer is gone for the rest of the year..." and in another thread "We'll look into this past 4.0." Sure it is experimental. But if you discover some bugs please do report it on bugtracker.

This is probably not the most important feature VirtualBox has produced, because you can move files to you guest with several other features like VirtualBox "shared folders" or using samba or similar. But I do agree with you if feature is present in VirtualBox it should be working, so bug report is the place to look to.

I think when responsible engineer will come back from new year's vacation he/she will fix the bug, so do report it on bugtracker!

[BuG]

BuG, as achimha has written: "The responsible engineer is gone for the rest of the year..." and in another thread "We'll look into this past 4.0."

Yes, I saw this.

Sure it is experimental.

But VirtualBox 4.0.0 is finally released as a major release. This feature is announced with it, but obviously not tested very well. That's what I don't understand.

so do report it on bugtracker!

No, I don't think so. I don't have the time for another registration, a new report and so on. I programmed a workaround for my shell extension, so I can live with it at the moment.

[abcuser]

But VirtualBox 4.0.0 is finally released as a major release. This feature is announced with it, but obviously not tested very well. That's what I don't understand.

This is open-source model, major testing is done by community and not internal QA.

No, I don't think so. I don't have the time for another registration, a new report and so on.

This will take you a 5 minutes max. Just the way it is, if you would like to use the latest version, then you have to be prepared that some new features are not working as expected. But if you report a bug, then you have a high probability that it will be fixed in first update (v4.0.2). But if you don't report a problem, then is just less possibility to be fixed - if someone else notice and report a problem.