Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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:
MyApp // Shared classes
MyApp.Droid // Android head
MyApp.iOS // iOS head
MyLibrary // The iOS version of our lib
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.
*** This bug has been marked as a duplicate of bug 28899 ***