The portable libraries are the response to the growing profile fragmentation in .NET frameworks. With help of portable libraries you can share code between different runtimes without dreadful
statements or even worse “Add as Link” source file sharing practices.
If you have an existing .net class library which you would like to reference from a different runtime (e.g. you have a .NET Framework 4.5 library which you would like to reference from a Windows Store project), you can either create a new portable class library and move the classes there or edit the existing .csproj file and change the XML directly. The following example shows how to convert a .NET Framework 4.5 library to a Portable Class Library.
First Unload the Project and change the following settings in the .csproj file:
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
and add the following keys to the first property group in order to get visual studio to show the framework picker dialog:
After that you can select the frameworks in the Library Tab of the Portable Library:
As last step, delete any framework references from the library as you have them already referenced via the .NET Portable Subset.
 Cross-Platform Development with the .NET Framework - http://msdn.microsoft.com/en-us/library/gg597391.aspx
 Framework Profiles in .NET: http://nitoprograms.blogspot.de/2012/05/framework-profiles-in-net.html
Friday, August 31, 2012 4:55 PM