Bug 14883 - Cannot copy file to output directory if the name contains brackets or special characters
Summary: Cannot copy file to output directory if the name contains brackets or special...
Status: RESOLVED DUPLICATE of bug 14847
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Martin Baulig
Depends on:
Reported: 2013-09-20 12:02 UTC by Curtis Wensley
Modified: 2014-02-09 13:37 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Reproduces the error (5.16 KB, application/zip)
2013-09-20 12:03 UTC, Curtis Wensley

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Curtis Wensley 2013-09-20 12:02:23 UTC
I've upgraded to Xamarin Studio 4.1.11, and my solution no longer builds due to output files that contain brackets in the name.  It gives me this error (full paths truncated for brevity):

/.../Microsoft.Common.targets: error : Cannot copy /.../MyFileToCopy %28with brackets%29.txt to /.../bin/Debug/MyFileToCopy (with brackets).txt, as the source file doesn't exist.

This does not happen with Xamarin Studio 4.0.12.
Comment 1 Curtis Wensley 2013-09-20 12:03:02 UTC
Created attachment 4942 [details]
Reproduces the error
Comment 2 Mikayla Hutchinson [MSFT] 2013-09-20 14:26:34 UTC
We're escaping the same way VS does. Looks like an xbuild bug. Fails with commandline xbuild too.
Comment 3 Mikayla Hutchinson [MSFT] 2014-02-09 13:37:45 UTC

*** This bug has been marked as a duplicate of bug 14847 ***