- Git New Branch
- Un-Reference PCL from iOS/Droid
- Remove PCL Project
- Move OLD PCL to another location
- Add New Project - Class Library
- Name it Just like your old PCL to Preserve Namespace or your going to have to be editing a TON of files...
- Place it where your old PCL was
- Re-Add Files from Old.PCL (MINUS BIN AND OBJ), Copy Folders from File Explorer to Project inside Visual Studio
- Edit .csproj of new project and add replace this:
<PropertyGroup> <TargetFramework>netstandard2.0</TargetFramework> </PropertyGroup>
with:
<PropertyGroup> <TargetFramework>netstandard2.0</TargetFramework> <PackageTargetFallback>$(PackageTargetFallback);portable-win+net45+wp8+win81+wpa8</PackageTargetFallback> </PropertyGroup>
- Open Packages.config in PCL.OLD in Editor
- Re-Add Nuget Packages manually, and you need to add every single one because it doesn't seem to add extras that are needed.
- Add Nuget Package Microsoft.NETCore.Portable.Compatibility
- Try a Re-build - Remove any incorrect Using; add any Nuget-'s you didn't see to add
- You may need to restart Visual Studio after this and try another clean and Rebuild. I had some weird error that went away. Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute
- Delete Assembly.cs in your Properties Fly-out in Solution Explorer
- Rebuild and you will see some ambiguous references, correct them all.
- Manage Nuget Packages for Solution -> Head over to Consolidate to make sure all package version is matched up
- Add refrence from your iOS/Droid to your new .NetCore Library!
Issues and Fixes
- Erroring on build w/ report on Xamarin.Forms.targets being null -> Remove all files in Properties (Assembly.cs, etc)
- When you try and build and you get Cannot find your net .Net Core dll -> Restart VS and rebuild (Files might be in use)
- You may have to delete the Obj and Bin directories of your new .NetCore a few times to get it to build...
- Fody and Realm.io Users, if you add or delete fody nuget packages like PropertyChanged.Fody, be prepared to delete Obj and Bin files for it to compile... (Update) Turns out the latest version of Fody doesn't play nice. Try 2.1.2 I believe.
- Was having many problems w/ Microsoft.BCL.*; ended up removing them and it worked out fine.
@ryanherman