CoreWiki throws Errors if only dotnet core 2.2 is installed

[cam-smith]

CoreWiki throws Errors if only dotnet core 2.2 is installed

[CubeSpark]

I created a fork and downloaded it from the Fritz source. I have the same problem - working on it now. I will try to install 2.1.

[CubeSpark]

In VS 2018, right-clicked on the Solution itself, and opened Build Order. It indicates a sequence:

1. CoreWiki.Core - I manually and successfully cleaned and built.

2. CoreWiki.Data.Abstractions - I manually and successfully cleaned and built.

3. CoreWiki.Data.EntityFramework - I manually and successfully cleaned and built, but with warnings:

   • ApplicationDbContext.cs(48,43,48,58):
     Warning CS0618: 'SlugHistoryDAO.AddedDateTime' is obsolete:
     'This property only exists for EF serialization purposes'

   • Repositories\SlugHistoryRepository.cs(39,5,39,18):
     Warning CS0618: 'SlugHistoryDAO.AddedDateTime' is obsolete:
     'This property only exists for EF serialization purposes'

4. CoreWiki.Notifications.Abstractions - I manually and successfully cleaned and built.

5. CoreWiki.Notifications - I manually and successfully cleaned and built.

6. CoreWiki.FirstStart - Failed.

   • StartupExtensions.cs(19,23,19,45):
     Warning CS0414: The field 'StartupExtensions._RunAfterConfiguration' is assigned
     but its value is never used.
   • StartupExtensions.cs(20,23,20,44):
     Warning CS0414: The field 'StartupExtensions._FirstStartIncomplete' is assigned
     but its value is never used.

   In the Areas folder, the Razor pages threw a warning first, then failed:
   ...Areas\FirstStart\Pages\Index.cshtml.cs(54,4,54,14):
   Warning MVC1002: 'HttpPostAttribute' cannot be applied to Razor Page handler methods.
   Routes for Razor Pages must be declared using the @page directive or using conventions.

   And: .nuget\packages\microsoft.aspnetcore.razor.design\2.2.0\build\netstandard2.0\Microsoft.AspNetCore.Razor.Design.CodeGeneration.targets(161,5): error : Assembly location for Razor SDK Tasks was not specified. The most likely cause is an older incompatible version of Microsoft.NET.Sdk.Razor, or Microsoft.NET.Sdk.Web used by this project.
   Please target a newer version of the .NET Core SDK.