Hello, I am using visual studio 2022, and I upgraded my previous .NET Framework project to .NET 6, but when I use the designer, it just keeps prompting "The designer is loading, you can use the designer in the background Continue to work while loading".
But when I rebuild a similar project step by step, it can work normally for a while, but most of the time it still stays at "Loading", and only "Creating VSCodeDomDesignerLoader" is displayed in the output log.
When I found the location where the log can be output in the options, I discovered why it scans the output file directory?
I placed the output directory in a separate partition due to other requirements. As a result, it scanned "System Volume Information" and was denied access. Why did the designer do this when opening it?
When I found this question and changed the output directory to a subfolder again, the designer worked. How to adjust the designer so that it will not affect the operation of the target folder in the root directory of the partition?
.NET Core Version: .NET 6.0.1
Have you experienced this same bug with .NET Framework?: NO
Hello, I am using visual studio 2022, and I upgraded my previous .NET Framework project to .NET 6, but when I use the designer, it just keeps prompting "The designer is loading, you can use the designer in the background Continue to work while loading".
But when I rebuild a similar project step by step, it can work normally for a while, but most of the time it still stays at "Loading", and only "Creating VSCodeDomDesignerLoader" is displayed in the output log.
When I found the location where the log can be output in the options, I discovered why it scans the output file directory?
I placed the output directory in a separate partition due to other requirements. As a result, it scanned "System Volume Information" and was denied access. Why did the designer do this when opening it?
When I found this question and changed the output directory to a subfolder again, the designer worked. How to adjust the designer so that it will not affect the operation of the target folder in the root directory of the partition?