Open PLDAWOL opened 2 months ago
@Olina-Zhang can your team investigate this please?
We have an existing similar designer issue: https://github.com/microsoft/winforms-designer/issues/5796, it also has the same verbose log:
fail: Request failures: Types/GetEditor.
14:14:35:411 Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: Could not resolve type, 'System.ComponentModel.ComponentEditor, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
Not sure if they have the same root cause.
Environment
Microsoft Visual Studio Professional 2022 Version 17.10.1 VisualStudio.17.Release/17.10.1+34928.147
.NET version
.NET 8.0
Did this work in a previous version of Visual Studio and/or previous .NET release?
.NET 4.6.1, .NET 4.7.2, .NET 4.8 .NetStandard 2.0
Issue description
I am writing on behalf of one of the project teams from Hitachi Energy, one of the partners of Microsoft.
After upgrade of our WinForms application projects from .NET 4.8 to .NET 8 we observed, that we are not able to edit WinForms using Designer anymore; we cannot add, move, remove or edit Properties of the controls.
We have followed some of the workarounds, but due to the sheer amount of projects (more than +100 in a solution) in our 20-year old app we haven't been succesful with this.
For single projects with forms when removed some of the project dependencies, then WinForms became editable again via OOP Designer.
We observed that for some reason the dependencies in our runtime somehow collide with OOP Designer dependencies or the logs are hiding some other problem while wrongly pointing out that the exception happens in the DesignServerTools.exe
Please advice how we could further approach troubleshooting such issue.
Due to confidentiality of content I was not able to produce project for repro. Also we do not know what we would need to reproduce, as we struggle to pinpoint what causes the issue.
Steps to reproduce
Diagnostics