Bug 58775 - Project no longer compiles after updating to VS 2017.3
Summary: Project no longer compiles after updating to VS 2017.3
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-08-15 15:55 UTC by Solvum Developer
Modified: 2017-08-15 16:37 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Solvum Developer 2017-08-15 15:55:52 UTC
I have also described the issue here - It does also contain a GitHub reference to reproduce the issue.


The very same project did compile with VS 2017.2
Comment 1 David Ortinau [MSFT] 2017-08-15 16:35:27 UTC
As you are probably aware is not explicitly netstandard compatible. The warnings are accurate. To get it to work at all you've done a workaround and benefited from a perhaps less aggressive compatibility check.

If you can, try updating to the pre-release of 2.3.5 where we've added the netstandard target to the Xamarin.Forms nuspec.

You may be able to get working in 15.3 as it was in 15.2 by adding a fallback to your csproj.


But in short, we aren't supporting in a netstandard scenario, and recommend you update to the next stable version which does.
Comment 2 Solvum Developer 2017-08-15 16:37:42 UTC
Hello David, as i was just about to post the solution here i received your email - applying the packagetargetfallback indeed does make the project compile again. Thanks for your answer.