VS 2017 v15.3.2 .NET Standard

RexHopeRexHope PHMember ✭✭

Hi everyone,

I am trying to create a new clean project with Xamarin, wherein I want to use .NET Standard library to be the primary code sharing lib (instead of the standard cross platform xamarin) I have done this a lot of times, however, I just updated my VS2017 to the latest one which is 15.3.2, and I've tried to create a new Xamarin project, and I encountered headache errors with Xamarin.

Problems:

  • ResolvedLibraryError with droid

Steps I have done when I create a new project
1. Insert a new project (.NET Standard)
2. Remove the PCL Project and move the App.xaml/.cs and MainPage.xaml/.cs to my .NET Standard
3. Include Xamarin.Forms pre-release on my solution
4. Set target fallback and debug type for my .NET Standard .csproj
5. Reference my .NET Standard to my droid project

Did someone experienced this when updating to the latest version of VS2017?
PS: Reason why I updated because latest version has the fix of intellisense of xaml files in .NET Standard.

Thanks for thy inputs! Any help would be appreciated.

Best Answer

  • RexHopeRexHope PH ✭✭
    edited August 2017 Accepted Answer

    Okay, I have fixed this.

    For those who have issues, do not drag/drop the App.xaml or whatever you have from the PCL/Shared project you have as it resulted on my end to have issues. So what I did was,
    1. I deleted the whole PCL library (including inside the project folder)
    2. Included a new content page xaml on my .NET Standard library
    3. And made it inherit the Application base class rather than the ContentPage (same goes with the xaml file)

    Such headache when using .NET Standard. Hope this helps.

Answers

  • RexHopeRexHope PHMember ✭✭
    edited August 2017 Accepted Answer

    Okay, I have fixed this.

    For those who have issues, do not drag/drop the App.xaml or whatever you have from the PCL/Shared project you have as it resulted on my end to have issues. So what I did was,
    1. I deleted the whole PCL library (including inside the project folder)
    2. Included a new content page xaml on my .NET Standard library
    3. And made it inherit the Application base class rather than the ContentPage (same goes with the xaml file)

    Such headache when using .NET Standard. Hope this helps.

Sign In or Register to comment.