Bug 37108 - Same-Name Projects
Summary: Same-Name Projects
Status: RESOLVED DUPLICATE of bug 28899
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: unspecified
Hardware: All All
: Normal normal
Target Milestone: (C7)
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2015-12-16 23:36 UTC by Anton Venema
Modified: 2015-12-19 20:12 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 28899

Description Anton Venema 2015-12-16 23:36:33 UTC
There is an old carryover from the MonoDevelop days that is still hanging around in Xamarin Studio - the inability to have two projects in the solution with the same name.

This isn't normally a huge deal, but we are seeing a big uptick in the number of clients wanting to use Xamarin.Forms and shared projects. In order for us to properly test our libraries to "officially" support this, we need to be able to add both the iOS and Android version of our component project, which have the same name, to our solution files for testing. You would typically do this by grouping the library projects into different solution folders, kinda like this:

    MySolution/
        MyApp               // Shared classes
        MyApp.Droid         // Android head
        MyApp.iOS           // iOS head
        iOS Libraries/
            MyLibrary       // The iOS version of our lib
        Android Libraries/
            MyLibrary       // The Android version of our lib

Visual Studio has long-supported this, but for it's never been supported in Xamarin Studio. Since we're are standardized on Mac OS X, we can't use Visual Studio, so we'd really love to see this make its way into Xamarin Studio.

This is currently the only obstacle preventing us from officially supporting Xamarin.Forms with our component, so we would appreciate either a timeline as to when this could be resolved, or an honest "no" if it won't be resolved so we can plan and inform our customers appropriately.
Comment 1 David Karlaš 2015-12-19 20:12:08 UTC

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