Resolve failure to resolve types with RSG

[captainsafia]

Build: https://dev.azure.com/dnceng/public/_build/results?buildId=1034221&view=logs&j=80f594f0-dab9-53e4-691e-a6c036ec4279&t=04eab92f-dbd1-567e-0acd-be26c7e1c779&l=2426

##[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?)

[Eilon]

I chatted with @captainsafia yesterday and I saw this happen once on my machine, which I erroneously assumed was bad luck. After I ran "Clean" on the project, the ever never showed up again. I hit it while adding/editing files to the Blazor WebView WPF sample. I am using VS2019 16.9.0 Preview 5 (public Preview channel).

[Eilon]

BTW I think that a workaround is to fully-qualify the namespace of the AppState type, that is, BlazorWpfSample.AppState or similar. Perhaps the _Imports.razor is not getting picked up?

[Eilon]

And indeed I applied the workaround to my PR and that made it pass on CI. So I'm guessing it's an issue with not seeing the @using's in the _Imports.razor file in some circumstances. (And clearly it's not VS-specific or VS Code-specific because it happened on CI.)

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Tratcher]

BlazorWasmHostedTemplate_AzureActiveDirectoryTemplate_Works has had a spike in failures since 6/26, the pass rate is down to 34%. Here's the most common one:

System.AggregateException : One or more errors occurred. (The file '/root/helix/work/workitem/uploads/AspNet.rndbabxhhx0.binlog' already exists.) (Object reference not set to an instance of an object.)
---- System.IO.IOException : The file '/root/helix/work/workitem/uploads/AspNet.rndbabxhhx0.binlog' already exists.
---- System.NullReferenceException : Object reference not set to an instance of an object.
----- Inner Stack Trace #1 (System.IO.IOException) -----
   at System.IO.FileSystem.LinkOrCopyFile(String sourceFullPath, String destFullPath) in System.Private.CoreLib.dll:token 0x6005b7b+0xa7
   at System.IO.FileSystem.MoveFile(String sourceFullPath, String destFullPath, Boolean overwrite) in System.Private.CoreLib.dll:token 0x6005b7d+0x92
   at System.IO.File.Move(String sourceFileName, String destFileName, Boolean overwrite) in System.Private.CoreLib.dll:token 0x60057fb+0x83
   at System.IO.File.Move(String sourceFileName, String destFileName) in System.Private.CoreLib.dll:token 0x60057fa+0x0
   at Templates.Test.Helpers.Project.CaptureBinLogOnFailure(ProcessEx result) in /_/src/ProjectTemplates/Shared/Project.cs:line 446
   at Templates.Test.Helpers.Project.RunDotNetPublishAsync(IDictionary`2 packageOptions, String additionalArgs, Boolean noRestore) in /_/src/ProjectTemplates/Shared/Project.cs:line 136
   at Templates.Test.BlazorTemplateTest.CreateBuildPublishAsync(String projectName, String auth, String[] args, String targetFramework, Boolean serverProject, Boolean onlyCreate) in /_/src/ProjectTemplates/BlazorTemplates.Tests/BlazorTemplateTest.cs:line 125
--- End of stack trace from previous location ---
----- Inner Stack Trace #2 (System.NullReferenceException) -----
   at Templates.Test.BlazorTemplateTest.DisposeAsync() in /_/src/ProjectTemplates/BlazorTemplates.Tests/BlazorTemplateTest.cs:line 60

[captainsafia]

These looks like issues with the test as opposed to issue with the source generator. Typically, issues with the source generator will surface out of the CSC process.

@HaoK Any thoughts on the issues above? Perhaps something addressed in your recent Blazor template tests PR?