It's possible to build applications without using visual studio at all (minus winrt apps, you need VS for that).
I know you're wrong about sqlite and linq as I've used them on both .net and mono. I think you're using the phrase "portable library" incorrectly. In the .net world, these are libraries created by microsoft that use the more limited version of the framework on their other platforms. For example, windows phone 7 and win rt use different portable libraries (a pain to manage, admittedly).
(ie. PCL --> One code base that compiles and runs on multiple c# runtimes; a key feature of writing cross platform c# applications)
Support is currently limited, see: http://docs.xamarin.com/ios/tutorials/Cross_Platform/Buildin...
Of course you can copy and paste your code into different projects manually, and compile it for a specific runtime. Or... you can use visual studio.
My personal preference is to just link source files and use partial classes (very much like the Linux kernel uses "pluggable" files to create a kernel) to create a product.
The problem is that there is no "Portable Class Library", there are dozens of profiles, and you need to pick the subset you want, for example: "Desktop and Windows8" is a much larger profile than "XBox and Silverlight", the subsets are different.
If you ignore Xbox and Silverlight, you pretty much have the whole stack everywhere.
Because I use LINQ and Sqlite on my shared code between Android and iOS. And you can even use Sqlite on Windows Phone (using Sqlite-cs) and Win8.
This is currently not possible using mono develop; the portable library support doesn't exist, which means your 'shared' libraries can't do things like use sqlite or linq; in fact, they can't have references to anything other than other portable libraries at all. Like, for example, system.collections.generic.