portable-class-library

I use and fancy Ninject alot. I wonder why there is no "BasicKernel" in Ninject.Portable? Is implementing IKernel require any call that PCLs don't contain? I'm talking about simple scenario (about: Bind<If1>().To<Class1>() and Get<If1>() )? The PCL version of Ninject is split into two libraries, Ninject.dll and Ninject.Common.dll as some of the code is platform-specific. Ninject cannot exist without its platform code. In order to use Ninject, you need to add the Portable.Ninject Nuget to both your portable library and to your main app/exe. Adding the package into the main app/exe is what

I'm building some code with these portable class libraries at present. I'm looking to target full .Net, WinRT Metro, Windows Phone, ... and then MonoTouch and MonoDroid. My experiments today show this can work - http://slodge.blogspot.co.uk/2012/04/experiments-with-portable-class.html However, I have hit a fairly significant problem - MonoTouch and MonoDroid currently support these libraries in that you can consume PCLs as binary assemblies, but they don't allow linking between project files e.g. I can reference MyLib.dll from a MonoDroid project, but I can't reference MyLib.csproj. This is a

I'm new to Nuget and I'm trying to create a NuGet package for a Portable Class Library project that has a package dependency on another portable class library I've created. I'm running into an issue where I'm receiving an error when calling nuget pack for the project file TestComponent2.csproj (I created this from the Portable for Universal Apps template in VS 2013). This library has a dependency on a nuget package created from another PCL called TestComponent1 . The package created never seems to contain this dependency (the console output even says "Dependencies: None"). However it is in the

In my PCL core project (WP8, Android, iOS, Xamarin, MvvmCross) I use custom attributes. The Type.GetCustomAttributes() extension method lets me examine the attributes used. Using PCL Profile104 this works well. But because I want to use async/await, I'll need to use PCL Profile78 (and .NET 4.5) Problem: Seems the GetCustomAttributes() and the Attributes property are not available in Profile78. Why?? Note: I am looking into the workaround by creating a PCL Profile 104 class library and wrapping the GetCustomAttributes() and then referencing this library from my PCL Profile78 library. However it

I'm needing to get some meta-data about the assembly which calls my component. As such, using Assembly.GetCallingAssembly() seems to be a natural fit. However, I've found it works everywhere except for in Windows Store. Where it's supported: Phone 7.0+ .Net 1.0+ Portable Class Libraries However, where it's not supported is directly within a Windows Store application. I can make a portable class library and then call it from there inside of a Windows Store application, but I can't just put it directly in the Windows Store app/class library. Is there a workaround for this or some other way to

I'm doing an Windows Phone app where I have a WebApi running in Azure. I'm using the new "Portable Class Library" (http://msdn.microsoft.com/en-us/library/gg597391.aspx) for my "Models" project which is of cause shared between my WebApi project (this is a normale ASp.NET MVC 4 project) and my Windows Phone project. This works great and the model (POCO) classes are serialized and deserialized just as I want. Now I want to start storing some of my Models/POCO objects and would like to use EF Code-first for that, but that's kind of a problem as I can't add the EntityFramework assembly to my

I am converting an existing multi-target Silverlight/.NET project to a Portable Class Library project in order to reduce the number of projects that are required to support multiple Microsoft platforms. I have an error in one class that is using the System.Security.Cryptography namespace The type or namespace name 'Cryptography' does not exist in the namespace 'System.Security' (are you missing an assembly reference?) This namespace is available in Silverlight and I am wondering why the Portable Class Library does not support it? One reason could be that this behaviour is by design: any