Quickstart sample throws exception with 4.7.2
See original GitHub issueDescribe the bug
A basic sample following the Quickstart throws the following exception on Build():
System.TypeLoadException: Method 'GetItem' in type 'NullRazorProjectFileSystem' from assembly 'RazorLight, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.
thrown at RazorLight.DefaultRazorEngine.get_Instance()
To Reproduce Steps to reproduce the behavior:
- Create new project for console app using 4.7.2
- Add code based on quickstart in main
namespace RazorLightTest
{
using System;
using System.Globalization;
using System.Threading.Tasks;
using RazorLight;
public class Program
{
static async Task Main(string[] args)
{
CultureInfo.CurrentUICulture = new CultureInfo("en-us");
var engine = new RazorLightEngineBuilder()
.UseEmbeddedResourcesProject(typeof(Program))
.UseMemoryCachingProvider()
.Build();
var template = "Hello, @Model.Name. Welcome to RazorLight repository";
var model = new ViewModel { Name = "John Doe" };
var result = await engine.CompileRenderStringAsync("templateKey", template, model);
Console.WriteLine(result);
}
public class ViewModel
{
public string Name { get; set; }
}
}
}
- Add RazorLight via “Manage NuGet packages…”
- Update all NuGet packages to latest version (make sure to uncheck “Include prelease”)
- Compile & Run
Expected behavior The application runs without problems and prints “Hello, John Doe. Welcome to RazorLight repository” to the console.
Information (please complete the following information):
- Windows 10
- .Net Framework 4.7.2
- 2.0.0-beta9
- package from NuGet
- Visual Studio Enterprise 2019
Additional context The best solution right now if of course not to update the NuGet packages but stick to the original versions. The downside is that depending on the context this could cause NuGet to show packages to consolidate.
So if the code does not work with the more recent versions I wonder if there is a way to restrict the versions e.g. setting a maximum version of ❤️.0 on the dependency in the package for .NET Standard
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (2 by maintainers)
Top GitHub Comments
Yes, if people are using packages.config, they are likely to have issues consuming .NET Core libraries.
Also see https://github.com/toddams/RazorLight/discussions/421#discussioncomment-957911