portable-class-library

I am trying to install MVVMCross NuGet package using NuGet 2.5 version. I have added the mono android and touch file to Profile104 folder. Still I am getting following exception: Attempting to resolve dependency 'MvvmCross.HotTuna.StarterPack (≥ 3.0.6)'. Attempting to resolve dependency 'MvvmCross.HotTuna.CrossCore (≥ 3.0.6)'. Attempting to resolve dependency 'MvvmCross.PortableSupport (≥ 3.0.6)'. Installing 'MvvmCross.PortableSupport 3.0.6'. Successfully installed 'MvvmCross.PortableSupport 3.0.6'. Installing 'MvvmCross.HotTuna.CrossCore 3.0.6'. Successfully installed 'MvvmCross.HotTuna

Object browser in Visual Studio 2012 offers two different component sets for Portable class libraries: .NET Portable Subset .NET Portable Subset (Legacy) When I create Portable Class Library it uses .NET Portable Subset. What is the second set and how can I use it? It contains MEF which is not available in .NET Portable Subset . Yep this is confusing, and is basically because Object Browser doesn't have a good way (and we couldn't add a way in this version without a significant rewrite) to represent the portable subset. To help shed some light on this, consider the following diagram: The

What is the exact difference between xamarin shared project and portable class library? When to use shared library and when to use portable class library? Is this possible to write native functionality in shared projects like showing alert,accessing camera and use it for both android and iOS? Can anyone please explain me. In shared projects each code file will be compiled for each destination (Android, iOS, Windows Phone etc). You are able to include platform specific code by using #if compiler directives. When you want to access the camera you need to write the access code inside an #if block

I am porting a .NET Framework C# class library to a Portable Class Library. One recurring problem is how to deal with classes decorated with the [Serializable] attribute, since this attribute is not part of the Portable Class Library subset. Serialization functionality in the Portable Class Library subset instead appears to be covered by DataContractAttribute . To preserve as much of functionality as possible in the Portable Class Library, is it sufficient to replace [Serializable] with the [DataContract] attribute (with the implication that all fields and properties subject to serialization

On MSDN I noticed a section about a Portable Class Library , under Version Information. See System.Object for an example. http://msdn.microsoft.com/en-us/library/system.object.aspx I did a brief Google search and couldn't find anything about the Portable Class Library . Does anyone here know what it is or where I could find more information about it? Ruben Bartelink UPDATE Oct 9 2017: Article comparing/constrasting .NET Core/Std/PCL UPDATE Nov 23 2016: Article by Rick Strahl UPDATE Oct 29 2016: .NETStandard 1->2 FAQ UPDATE Oct 19 2016: This is the best interview/video I've seen to date

I am building new application for Desktop, Windows 8 store and Windows phone at the same time. so I created Portable Class library to have common functionality across all platforms. my problem is that when I try to reuse my code inside PCL I can not access some methods and properties inside library. According to MSDN those methods are supported but I do know now why I can not access them. var property = memberExpression.Member as PropertyInfo; if (property == null) { } var getMethod = property.GetGetMethod(true); if (getMethod.IsStatic) {} here is the fragment of the code that can not be

Is anybody explain to me what is the advantage of using portable class libraries instead of using "Add as Link"? Thanks Disadvantages of linked files: Add as link can be hard to maintain, especially as you scale to multiple projects and many source files. Tooling (such as Project Linker for Visual Studio 2010, or holding ALT while dragging in Visual Studio 2012) can make this easier. Refactoring tools don't work with linked files. For example, if you rename a class or method in a linked file, refactoring tools won't update references to other linked copies of that API. When editing code in a