Bug 11028 - Unable to load projects with %20 in their name from the Start Screen
Summary: Unable to load projects with %20 in their name from the Start Screen
Status: RESOLVED DUPLICATE of bug 30252
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-03-10 19:16 UTC by Shmueli Englard
Modified: 2015-08-25 06:43 UTC (History)
2 users (show)

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

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 Developer Community or GitHub 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 Shmueli Englard 2013-03-10 19:16:43 UTC
I have project that's hosted in GIT with "spaces" encoded as "%20" in the folder path. When selecting a project to open Xamarin Studio is able to open the project fine but if I try to use the project from the start screen's recent project list it fails with "File not found".

Steps to reproduce the problem:
1. Create Project in folder and have the folder use %20 instead of "space".
2. Open project in Xamarin Studio using Open Project.
3. Restart Xamarin Studio.
4. Try to open project from Recent Projects list on start screen.
Comment 1 Lluis Sanchez 2015-08-25 06:43:00 UTC

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