Linker issues and PCL

[dazinator]

At the moment, we have several projects - some with NuGet packages, that are targeting full .net framework. (Security, Data etc)

When these projects are referenced from monotouch, the Linker complains because it discovers references to types that it can't resolve on the monotouch platform.

Really, these projects could do with being PCL projects so that we know the code compiled in them (and the NuGet packages / references added to them) are cross platform compatible.

Until this can be done the only way to proceed is to disable the linker for these projects, which also means that we are allowing unsafe code into the app (i.e code that may at any point request a type that doesn't exist)

• [ ] Get rid of Reach.GCTactical.Security project, and just implement a ICryptoProvider service (in Reach.GCTactical) with the methods we need. Can use some PCL compatible library to perform the actual crypto algorithms.
• [ ] Make Reach.GCTactical.Data project a PCL. Could optionally move the classes into the Reach.GCTactical (PCL) project keeping the same namespaces.

[dazinator]

@jamesreach - I will aim to do this after I finish table routing next week, otherwise anyone can feel free to pick this up.