Resolve failure to resolve types with RSG
See original GitHub issue##[error]D:\workspace\_work\1\s\src\Components\WebView\Samples\BlazorWpfApp\Microsoft.NET.Sdk.Razor.SourceGenerators\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\_Pages_Index.razor.cs(126,75): error CS0246: (NETCORE_ENGINEERING_TELEMETRY=Build) The type or namespace name 'AppState' could not be found (are you missing a using directive or an assembly reference?)
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
How to Resolve Errors in GTA Online about Strict NAT Type
To resolve this issue, put your gateway into 'Bridge Mode' so that only your router performs NAT.
Read more >c# - Type resolve fails for types with strange name (2.5.29.35)
I have a .NET app where I log failures to resolve types that are supposed to be loaded in the current domain. I...
Read more >How To Fix Failed to Connect to the Rockstar Games Library ...
In This Video We Will See How To Fix Failed to Connect to the Rockstar Games Library Service Error - GTA V Launcher...
Read more >Restore of Exchange Database to RSG is failing with the ...
Restore of Exchange Database to RSG is failing with the following error message, E8605 Failed to start restore, EC=Invalid user ID or password ......
Read more >Inbound Call Failed on Response Group Service
During that moment, I thought of the most simplest method to resolve this issue is to recreate the entire RSG object as it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Test needing to be unquarantined: https://github.com/dotnet/aspnetcore/blob/c1d16e3ccd2df6a3ff06b7e0233ad96fe6113d5b/src/ProjectTemplates/BlazorTemplates.Tests/BlazorWasmTemplateTest.cs#L393
Not yet eligible for unquarantining by our “30 day rule”
Marking this as
test-fixed
per the above discussion.We believe this has been resolved already. Unfortunately, there is no clear link to actual change which may have resolved this. Moving this to 6.0 to unquarantine the old flaky test.