Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The name 'section' does not exist in the current context in .net core 3
See original GitHub issueDescribe the bug
Since upgrading to the latest version of Razorlight official release (I was using unofficial before) I am experience the issue that sections aren’t working anymore. I keep getting the error: The name 'section' does not exist in the current context.
To Reproduce I am working on a unit test which coverage this breakage
Expected behavior
Information (please complete the following information):
- OS: Ubuntu
- Platform .net Core 3.0
- RazorLight version 2.0-beta4
- Are you using the OFFICIAL RazorLight package? Yes
- Visual Studio version I am using Rider 2019.3
Additional context I had to upgrade from the unofficial package to the official beta 4 because it has net core 3 support before I was using the .net core 2.2 which worked happilly
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:28
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for your efforts on this project.
Just wondering if there has there been any progress on this issue? Seems can’t use RazorLight version 2.0-beta4 in .net core 3.1 if you define a @section ?
Can you show me a repro? Is this problem related to sections or should you open a new issue so we can discuss your problems there? Thanks.