With the standard image, the eMMC is 97% full. I suspect that it won’t all fit (though I have nothing more concrete than a gut sense that it’s too tight), and in general, I prefer to leave the eMMC for production images, not works-in-progress. It’s easier to recover from mishaps with an SD card. There are two options for making things fit in eMMC:
- Trim down the install by removing things you don’t need and installing mono-runtime (or mono-devel) and selected lib packages.
- Install snappy, yocto or some other distro that is slimmer and more tuned to IoT than hobbyist use.
Both of those are beyond the scope of the KB I was writing, though I do have articles in the works on both of those.
The eMMC boots much faster (10-20 seconds, depending on your network config and whether you are launching a gui), and I would prefer to use it as the primary OS partition, but for development, I care more about having all the tools there. Later, I will optimize down and spin a custom Yocto or Snappy image, with Docker for deployment and updating.
Note that the Verdant system will soon handle this all for you automatically. You will install a custom Yocto-based kernel with Docker and vpn support, and then Verdant deploys direct to your device. This is currently in testing, and will work alongside the current native and netmf support. Verdant will be in open beta in January 2017.
EDIT: Edited to clarify some points