New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timed out while connecting to named pipe: DesignToolsServer #6420
Comments
@Shyam-Gupta / @RussKie can you guys take a look here and map it to the issue in designer repo? |
Hello, someone? |
Linking the similar bugs together #6492. I am guessing they both have same root cause. |
@nathan130200 Could you please share |
I had the same problem today. The solution was to upgrade the project's version from .net 5 to .net 6 or remove the reference project with the highest version and delete the contents of the temp folder. |
I was able to successfully work around this issue for myself and my team in a 110 project solution. We added the DesignToolsServer.exe to Windows Defender exceptions so that it is not slowed down by the system call hooks Defender uses to provide real-time protection. The issue has not gone away completely but is now only a minor inconvenience since once the server has started it persists for the lifetime of the Visual Studio run. Add-MpPreference -ExclusionProcess 'DesignToolsServer.exe' |
@Shyam-Gupta i had same issue, first time show exception "Timeout while connecting remote pipe", next time i try open form, don't show up any logs, neither on Windows Event Viewer also: sigWZTKt8g.mp4Its a fresh winforms project. |
Also in taskmgr don't show up, DesigntToolsServer trying to start 6jAXTGIfZs.mp4Once its crash first time, design tools server don't attempt to start again even if i open any form/control. |
@nathan130200 Thank you so much for sharing the videos. The error regarding I created a new Please let me know if you have other Visual Studio versions installed side by side on the same machine. You mentioned that the error reproes even for new WinForms projects. Let me know if you are using Visual Studio new project creation wizard or dotnet.exe command line tool to create the project. Do you see any error if you create a 6.0 WinForms project, build it and then try to launch the project exe directly from its In mean time, I will try to add more diagnostic logs in the product and get back. Thanks again for working with me to get to the root cause of this problem. FYI: @merriemcgaw |
I just have VS2022 preview installed, also i did some tests, if i close and reopen project DesignToolsServer was able to start. But its a bit confused. I think isn't supposed to i be forced to close/reopen project, specially some big projects that take some times to load. Also building and running directly from .exe or debugging inside VS works fine, just designer don't start at once. |
@nathan130200 Earlier designer was copying all the files present in project output directory to a temp folder from where Hence I request you to try the scenario in |
Happened in Current(stable) sersion visual studio 2022 with a C#(net6.0-windows) project and I believe it is the same issue. After switching to Preview(17.1.0 Preview 3), it shows
|
I solved this by removing this section from the csproj file:
|
In my situation, i just type An workaround is close and reopen entire solution to make designer works, but isn't correct specially for big projects. |
@nathan130200 I wasn't able to repro on my machine - |
The problem, is VS don't launch design tools server for the first time, idk what cause this. But at second time (after unload/reload entire solution), vs was able to copy design tools server and start. The first time, VS attempt to connect to design tools server pipe, without begin started, so this cause "Timeout connecting to named pipe" because VS is waiting for connection to IPC, but since IPC never was requested to start for first time then cause exception. Like i've said this happened since they release winforms for .net core, i was unable to start any project that uses winforms and new winforms designer (that i think is DesignToolsServer). I will try record again to show. I will wait for next preview and test if was solved, seems to be internal problem on visual studio not proper launching design tools server |
Thanks for the update. Given that this isn't happening to everyone I'm very curious about why it is happening on your installs. We will be adding more logging coverage and other diagnostic services so that we can better figure out what is impacting our customers. We'll let you know when that work is in a Preview so we can test it out together. |
As an update. |
Hi @nathan130200, it looks like you just commented on a closed issue. The team will most probably miss it. |
.NET Core Version:
.NET 6.0.100
.NET Info Command
No
Problem description:
Attemt to open winforms designer on NET6 fail everytime.
If i both add
<TargetPlatforms>net472;net6.0-windows</TargetPlatforms>
for both net6.0-windows and net472, the designer open, but open old .NET Framework designet (that works too for .net 6), but i must be forced to reference net framework in csproj.Since .net core/net 6 desktop support, the designer NEVER WORKED.
Stuck on this:
Expected behavior:
Open winform designer.
Minimal repro:
Create empty winform project on VS2022 and try open
Form1
designer.Output from VS2022:
Sometimes in Output window only display first line:
[16:30:43.1921519] Creating VSCodeDomDesignerLoader
dotnet new
command targeting windows desktop:Steps i tried:
None of these worked.
3jRwY9y3qk.mp4
The text was updated successfully, but these errors were encountered: