maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
dotnet-core/release-notes/3.0/preview/3.0.0-preview-known-issues.md
N. Taylor Mullen 64ee350e35
Add referencing 3.0.0 project limitations 
- Added 3 bullet points to encompass 1 primary issue. Basically, referencing any MVC 3.0 library doesn't work as intended. Called out specific use cases of each failure to make the known issues list easier to navigate.
2019-03-06 17:21:26 -08:00

3 KiB
Raw Blame History

.NET Core 3.0 Preview Known Issues

This document lists known issues for .NET Core 3.0 Preview releases which may be encountered during usage.

ASP.NET Core

Preview 3

  • Updates to .razor files fail to show up in subsequent builds: Updates to Razor Component (.razor) in Visual Studio may fail to show up in subsequent builds. To work around this issue add the following item group to the project file:

    <ItemGroup>
    <UpToDateCheckInput Include="@(Content->WithMetadataValue('Extension', '.razor'))" />
</ItemGroup>

  • Updates to Razor Components in .razor files fail to show up in IntelliSense: Updates to Razor Components defined in .razor files may fail to show up in IntelliSense in Visual Studio. To workaround this issue rebuild the project.

  • Single Page Applications with authentication enabled throws method not found exception when visiting the register or login pages: The exception message is the one below. Method not found: 'Microsoft.EntityFrameworkCore.Metadata.Builders.IndexBuilder Microsoft.EntityFrameworkCore.Metadata.Builders.EntityTypeBuilder``1.HasIndex(System.Linq.Expressions.Expression``1<System.Func``2<!0,System.Object>>)'. To workaround this issue follow these steps:

    • Replace the following package references with the ones below in your csproj folder:

      <PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="3.0.0-preview3-19153-02" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="3.0.0-preview3.19153.1" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="3.0.0-preview3.19153.1" />

      <PackageReference Include="Microsoft.AspNetCore.Identity.EntityFrameworkCore" Version="3.0.0-preview-18579-0056" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="3.0.0-preview.19080.1" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="3.0.0-preview.19080.1" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Relational" Version="3.0.0-preview.19080.1" />
<PackageReference Include="Microsoft.EntityFrameworkCore" Version="3.0.0-preview.19080.1" />

    • Add the following snippet to your csproj file:

      <PropertyGroup>
  <NoWarn>$(NoWarn);NU1605</NoWarn>
</PropertyGroup>

  • Referencing a 3.0.0 Razor class library with Razor pages 404s: Razor pages in 3.0.0 Razor class libraries can not be routed to. To workaround this issue re-target the Razor class library to any pre-3.0 netstandard.

  • Referencing a 3.0.0 MVC library does not work: ApplicationParts, Controllers, Views, etc. are not discoverable in a referenced 3.0.0 MVC library. The only current way to workaround this issue is to re-target the MVC library to pre-3.0 netstandard.

  • Integration testing a MVC 3.0.0 app does not work: Integration testing a MVC 3.0.0 app does not work. The only current way to workaround this issue is to re-target the MVC app to pre-3.0 netcoreapp.