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 for Bug 1711 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I have a VS.NET 2008 library project that MD opens fine. But I want to convert to target MonoTouch ("Mono for iPhone"). There is no way under Build->General to do this and I could not see any tool.
Hacking ProjectTypeGuids by hand is something I'd like to avoid.
Also, it would be good if all of the existing configurations such as Debug|iPhone Simulator could be created by same option/tool.
I think this is a pretty standard need given folks will bring over their code libraries (although I just create an XXX-MT.csproj since I have a single source code tree).
I don't know if MD has a way of handling this kind of thing. It does already support migrating projects from an old version of the csproj format to a new version so it would be easy enough on a technical level to take an arbitrary project type and do a mostly automated conversion to another type. I just wonder what UI would be required for this and what the workflow should be like. Also what combinations should this support. Finally, how would this idea mesh with our existing plans to simplify creating monotouch/mono for android projects out of regular desktop solution files.
Conversions aren't going to be trivial, since we can't blindly copy properties, configurations, etc. It's not too hard but it does require some thought, especially the UX.
Regarding UX, this should be accessible from the project linker (filelist syncing between projects) when we have that - so users can directly create a linked project of a different type. It would be useful to be able to create a portable library project from a desktop/MT/M4A/SL library, when we have PLP support.