Q: How to best support multi-platform (i.e Xamarin) projects
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Our team has an enterprise-sized Xamarin mobile solution consisting of over 30 projects -- Android/iOS/PCL. We're switching to Paket because nuget's been...a lot of work, to say the least. ;)
However, because our projects have many package dependencies (60+ in some cases), and the packages target 3+ platforms, Paket's conditional framework code bloats each csproj file by thousands of lines into an unmanagable size. The automatic framework detection does not work (probably because Xamarin projects literally say like "v5.0" for TargetFrameworkVersion on Android). Specifying the correct framework on 60 references * 30 paket.references files also seems pretty unmaintanable.
Any suggestions?
Edit: Should we somehow fix automatic framework targeting?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how framework detection handles the TargetFrameworkVersion values in the Android projects, then compare that with the conditional framework entries generated in the csproj files and the settings in the paket.references files. A useful outcome would be a decided, maintainable approach for multi-platform Xamarin projects, with framework detection or configuration behavior validated against the reported project structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios
- Domain
- mobile, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100