Closed AlessandroMenchiniTmaxLab closed 1 year ago
@AlessandroMenchiniTmaxLab During launch, designer spawns DesignToolsServer
process which loads the .NET dlls referenced by the project, to find available Types
. If a dll is not available, we log the error. But this should not affect designer functionality unless those Types
are used in the code.
@AlessandroMenchiniTmaxLab During launch, designer spawns
DesignToolsServer
process which loads the .NET dlls referenced by the project, to find availableTypes
. If a dll is not available, we log the error. But this should not affect designer functionality unless thoseTypes
are used in the code.
Thanks for the clarification Shyam-Gupta. Seeing these errors in the log and noting some slowdowns in the designer I thought these errors were related in some way.
@AlessandroMenchiniTmaxLab We have addressed several designer performance issues in recent VS releases, and we will continue to do so. Please log a new bug with details about the designer slowdowns you are experiencing and we will investigate them. Thank you.
Thanks @AlessandroMenchiniTmaxLab, I'm glad this issue turned out not to be a major thing. Please feel free to create an issue with full logs if you have further troubles.
During launch, designer spawns
DesignToolsServer
process which loads the .NET dlls referenced by the project, to find availableTypes
. If a dll is not available, we log the error. But this should not affect designer functionality unless thoseTypes
are used in the code.
fail
should denote only critical issues, which prevent the designer from functioning. If this isn't a critical issue, then perhaps the log level should be dialled down to a warning.
Environment
Visual Studio Community 2022 (64bit) version: 17.5.0
.NET version
.net 6.0
Did this work in a previous version of Visual Studio and/or previous .NET release?
No response
Issue description
Steps to reproduce
opening a Form in designer
Diagnostics